Skip to content
vulnerability

CVE-2025-24201

10.0
Critical
KEV · Exploited in wildEPSS 4%Patch available

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.).

exploited
Yes, in CISA KEV since 13 Mar 2025fix by 3 Apr 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 3.8%
Published 11 Mar 2025Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · networkCWE-787· Out-of-Bounds Write

Can a WAF block it? No. The vulnerability is triggered by maliciously crafted web content, which is delivered via HTTP requests to the Safari browser or related Apple OS web components. The description does not specify any unusual request patterns that a web application firewall could reliably detect without blocking legitimate traffic.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopechangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
common questions

Is CVE-2025-24201 being exploited?

Yes. CVE-2025-24201 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-24201?

CVE-2025-24201 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-24201?

Yes. A fix has been recorded for CVE-2025-24201. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-24201 affect?

CVE-2025-24201 affects apple:safari, apple:macos, apple:visionos, apple:watchos, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
apple:safariapple:macosapple:visionosapple:watchosapple:ipadosapple:iphone_osdebian:debian_linux
affected versions
Apple iOS and iPadOS
  • affected< 15.8.4
  • affected< 16.7.11
  • affected< 18.3.2
Apple iPadOS
  • affected< 17.7.6
Apple macOS
  • affected< 15.3.2
Apple Safari
  • affected< 18.3.1
Apple visionOS
  • affected< 2.3.2
Apple watchOS
  • affected< 11.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 12 Nov 2025 (SSVC 2.0.3).

timeline

  1. 11 Mar 2025Published
  2. 13 Mar 2025Added to CISA KEV (exploited in the wild) · 1 day later
  3. 3 Apr 2025CISA remediation due date (US federal agencies) · 21 days later
  4. 11 Jul 2025First proof-of-concept repository on GitHub (unvetted) · 99 days (about 3 months) later
  5. 12 Nov 2025CISA SSVC assessment: exploitation active · 125 days (about 4 months) later
  6. 2 Apr 2026CVE record last updated · 141 days (about 5 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 214 days (about 7 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
21 references in the CVE record: 21 links
Show 13 more

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved