dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Apr 2025.
SafariWeb browser · Apple

CVE-2025-24201

CRITICAL · 10.0 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 2.3.2 / 11.4 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
An out-of-bounds write issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in Safari 18.3.1, iOS 15.8.4 and iPadOS 15.8.4, iOS 16.7.11 and iPadOS 16.7.11, iOS 18.3.2 and iPadOS 18.3.2, iPadOS 17.7.6, macOS Sequoia 15.3.2, visionOS 2.3.2, watchOS 11.4. Maliciously crafted web content may be able to break out of Web Content sandbox. This is a supplementary fix for an attack that was blocked in iOS 17.2. (Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 17.2.).

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

An out-of-bounds write vulnerability in WebKit allows malicious web content to escape the Web Content sandbox, potentially enabling arbitrary code execution. This is a supplementary fix for an attack that was originally blocked in iOS 17.2, and Apple reports active exploitation in highly sophisticated targeted attacks against specific individuals on older iOS versions.

MitigationImmediately update all affected Apple devices to the patched versions (iOS 18.3.2/iPadOS 18.3.2 or later, iOS 16.7.11, iPadOS 17.7.6, macOS Sequoia 15.3.2, Safari 18.3.1, visionOS 2.3.2, watchOS 11.4). For devices running iOS versions before 17.2 that cannot be updated, consider restricting web browsing or implementing additional network-level controls.

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.3.1
Debian LinuxOperating system
Affected:= 11.0
macOSOperating system
Affected:>= 15.0, < 15.3.2
VisionosOperating system
Affected:< 2.3.2
WatchosOperating system
Affected:< 11.4
IpadosOperating system
Affected:>= 15.8, < 15.8.4>= 16.7, < 16.7.11>= 17.0, < 17.7.6>= 18.0, < 18.3.2
Iphone OsOperating system
Affected:>= 15.8, < 15.8.4>= 16.7, < 16.7.11>= 17.0, < 18.3.2

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify iOS or iPadOS version
    Go to Settings > General > About on the device and note the version number (e.g., 17.5, 18.1)
    Affected if Version is 15.8.x, 16.7.x, 17.0-17.7.5, or 18.0-18.3.1 (any version before 15.8.4, 16.7.11, 17.7.6, or 18.3.2)
  2. Identify macOS version
    Click Apple menu > About This Mac and note the macOS version (e.g., 15.2, 15.3)
    Affected if Version starts with 15.0, 15.1, or 15.3.0-15.3.1 (any version before 15.3.2)
  3. Identify Safari version on macOS
    Open Safari, go to Safari menu > About Safari to see the build version
    Affected if Safari version is earlier than 18.3.1 (compare your version to 18.3.1)
  4. Identify watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About and note the watchOS version
    Affected if Version is earlier than 11.4 (any version below 11.4)
  5. Identify visionOS version
    Go to Settings > General > About on the Vision Pro device and note the version
    Affected if Version is earlier than 2.3.2 (any version below 2.3.2)

The environment is affected if any Apple device runs an OS or Safari version that falls within the affected ranges: iOS/iPadOS 15.8-15.8.3, 16.7-16.7.10, 17.0-17.7.5, 18.0-18.3.1; macOS 15.0-15.3.1; Safari before 18.3.1; watchOS before 11.4; visionOS before 2.3.2.

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.3.2 / 11.4 / 15.3.2 or later
Fixed in 2.3.211.415.3.2
Interim mitigation

Immediately update all affected Apple devices to the patched versions (iOS 18.3.2/iPadOS 18.3.2 or later, iOS 16.7.11, iPadOS 17.7.6, macOS Sequoia 15.3.2, Safari 18.3.1, visionOS 2.3.2, watchOS 11.4). For devices running iOS versions before 17.2 that cannot be updated, consider restricting web browsing or implementing additional network-level controls.

Recommended fix High confidence

Apple: Safari 18.3.1, iOS 18.3.2, iPadOS 18.3.2, macOS 15.3.2, visionOS 2.3.2, watchOS 11.4 | Debian: No vendor patch listed in sources - upgrade to Debian 12 or later

  1. Update Safari to version 18.3.1 or later
  2. Update iOS devices to iOS 18.3.2 (or iOS 15.8.4/16.7.11 if staying on older major versions)
  3. Update iPadOS devices to 18.3.2 (or 15.8.4/16.7.11/17.7.6 for older major versions)
  4. Update macOS to Sequoia 15.3.2
  5. Update visionOS to 2.3.2
  6. Update watchOS to 11.4
  7. For Debian 11.0, check for vendor security updates or consider upgrading to a newer Debian release
Caveat Standard OS update risks apply (rare compatibility issues with older apps) - back up device before updating

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

Fix this in Safari Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24201 — 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-24201 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