dbcve.org
SafariWeb browser · Apple

CVE-2025-24264

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 15.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The issue was addressed with improved memory handling. This issue is fixed in Safari 18.4, iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4. Processing maliciously crafted web content may lead to an unexpected Safari crash.

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 · moderate confidence

A memory handling vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected Safari crash. The high CVSS score suggests potential for memory corruption that could be leveraged for more serious exploitation beyond just denial of service.

MitigationApply vendor-supplied security updates: Safari 18.4, iOS 18.4/iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, and watchOS 11.4.

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.4
IpadosOperating system
Affected:< 17.7.6>= 18.0, < 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 15.0, < 15.4
TvosOperating system
Affected:< 18.4
VisionosOperating system
Affected:< 2.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check Safari version on macOS
    Open Safari, go to Safari > About Safari to view the version number
    Affected if The version is earlier than 18.4 (e.g., 18.3.x or lower)
  2. Check iOS version on iPhone
    Go to Settings > General > About to view the iOS version
    Affected if The version is earlier than 18.4, or between 18.0 and 18.3.x, or earlier than 17.7.6 (for iPadOS)
  3. Check iPadOS version on iPad
    Go to Settings > General > About to view the iPadOS version
    Affected if The version is earlier than 18.4, or between 18.0 and 18.3.x, or earlier than 17.7.6
  4. Check macOS version
    Go to Apple menu > About This Mac to view the macOS version
    Affected if The version is 15.0 through 15.3.x (any version from 15.0 up to but not including 15.4)
  5. Check tvOS version
    Go to Settings > General > About to view the tvOS version
    Affected if The version is earlier than 18.4
  6. Check visionOS version
    Go to Settings > General > About to view the visionOS version
    Affected if The version is earlier than 2.4

A device is affected if its Safari, iOS, iPadOS, macOS, tvOS, or visionOS version falls within the specified vulnerable ranges AND the WebKit browser component can process untrusted web content.

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.4 / 15.4 / 17.7.6 or later
Fixed in 2.415.417.7.6
Interim mitigation

Apply vendor-supplied security updates: Safari 18.4, iOS 18.4/iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, and watchOS 11.4.

Recommended fix High confidence

Safari 18.4, iOS 18.4, iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4

  1. Ensure your device is connected to the internet and has sufficient battery charge
  2. On iPhone/iPad: Go to Settings > General > Software Update and install the available update (iOS 18.4 or iPadOS 18.4/17.7.6)
  3. On Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.4
  4. On Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4
  5. On Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4
  6. On Apple Watch: Go to Settings > General > Software Update and install watchOS 11.4
  7. On Safari (if standalone): Update to Safari 18.4 via macOS update or Software Update
  8. After updating, verify the Safari version matches the fixed release

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-24264 — 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-24264 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