dbcve.org
SafariWeb browser · Apple

CVE-2025-43227

HIGH · 7.5 CVSS v3.1 Published 2025-07-30
Fix available
A fix is available. Upgrade to 2.6 / 11.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This issue was addressed through improved state management. This issue is fixed in Safari 18.6, iOS 18.6 and iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6. Processing maliciously crafted web content may disclose sensitive user information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A state management flaw in WebKit allows processing of maliciously crafted web content to disclose sensitive user information. The vulnerability stems from improper handling of state in the browser engine, allowing attackers to access data that should be protected.

MitigationApply the vendor-supplied patches by updating to Safari 18.6, iOS/iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, or watchOS 11.6 as appropriate for affected devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SafariWeb browser
Affected:< 18.6
IpadosOperating system
Affected:< 18.6
Iphone OsOperating system
Affected:< 18.6
macOSOperating system
Affected:< 15.6
TvosOperating system
Affected:< 18.6
VisionosOperating system
Affected:< 2.6
WatchosOperating system
Affected:< 11.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal
    Affected if Version is below 18.6
  2. Check iOS or iPadOS version
    Go to Settings > General > About on iPhone or iPad, or run 'idevicesyslog' or check via Finder/Apple Configurator
    Affected if Version is below 18.6
  3. Check macOS version
    Click Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if Version is below 15.6 (Sequoia)
  4. Check tvOS version
    Go to Settings > General > About on Apple TV, or check via Finder (when device is in recovery mode)
    Affected if Version is below 18.6
  5. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro
    Affected if Version is below 2.6
  6. Check watchOS version
    Go to Settings > General > About on Apple Watch via iPhone Watch app, or on the watch itself
    Affected if Version is below 11.6

You are affected if any Safari browser or Apple operating system (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) on your device is running a version lower than the fixed release (18.6, 15.6, 2.6, or 11.6 respectively).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6 / 11.6 / 15.6 or later
Fixed in 2.611.615.6
Interim mitigation

Apply the vendor-supplied patches by updating to Safari 18.6, iOS/iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, or watchOS 11.6 as appropriate for affected devices.

Recommended fix High confidence

Safari 18.6, iOS 18.6, iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6

  1. Update Safari to version 18.6 or later
  2. Update iOS (iPhone) to version 18.6 or later
  3. Update iPadOS to version 18.6 or later
  4. Update macOS to Sequoia 15.6 or later
  5. Update tvOS to version 18.6 or later
  6. Update visionOS to version 2.6 or later
  7. Update watchOS to version 11.6 or later
  8. After updating, verify the version in Settings > General > About (iOS/iPadOS), System Settings > About (macOS), or the respective Settings app for each device
Caveat Apple minor version updates typically include bug fixes and security patches with minimal risk of breaking changes; however, always review release notes for any known compatibility issues before updating production devices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43227 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data