dbcve.org
SafariWeb browser · Apple

CVE-2025-24213

HIGH · 7.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 15.4 / 17.7.6 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 with improved handling of floats. This issue is fixed in Safari 18.5, iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. A type confusion issue could lead to memory corruption.

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 type confusion vulnerability in WebKit's float handling in Safari and other Apple products allows memory corruption. The issue was addressed with improved handling of floats and is fixed in the listed Safari 18.5, iOS 18.5, iPadOS 17.7.7/18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, and watchOS 11.5 releases.

MitigationApply the vendor-supplied updates for affected Apple products (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) to the fixed versions listed in the CVE advisory.

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

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 menu > About Safari. Note the version number shown.
    Affected if Version is earlier than 18.4 (or 18.5 and later is fixed)
  2. Check iOS version on iPhone
    Go to Settings > General > About. Note the iOS version number.
    Affected if Version is earlier than 18.4 (iOS 18.5 and later is fixed)
  3. Check iPadOS version on iPad
    Go to Settings > General > About. Note the iPadOS version number.
    Affected if Version is earlier than 17.7.6 OR between 18.0 and 18.4 (17.7.7 and 18.5+ are fixed)
  4. Check macOS version
    Go to Apple menu > About This Mac. Note the macOS version (e.g., 15.4 Sequoia).
    Affected if Version is 15.0 through 15.4 (15.5 Sequoia and later is fixed)
  5. Check tvOS version on Apple TV
    Go to Settings > General > About > Version. Note the tvOS version number.
    Affected if Version is earlier than 18.4 (tvOS 18.5 and later is fixed)

You are affected if any Apple device runs Safari, iOS, iPadOS, macOS, or tvOS versions within the affected ranges listed; the vulnerability is fixed in Safari 18.5+, iOS 18.5+, iPadOS 17.7.7+/18.5+, macOS 15.5+, and tvOS 18.5+.

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 15.4 / 17.7.6 / 18.4 or later
Fixed in 15.417.7.618.4
Interim mitigation

Apply the vendor-supplied updates for affected Apple products (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) to the fixed versions listed in the CVE advisory.

Recommended fix High confidence

Upgrade to Safari 18.5, iOS 18.5, iPadOS 18.5 (or 17.7.7 for iPadOS 17.x), macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as applicable

  1. Identify the affected Apple device (iPhone, iPad, Mac, Apple Watch, Apple TV, or Vision Pro)
  2. Determine the current installed OS version via Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
  3. For iPhone/iPad: Go to Settings > General > Software Update and install the latest available update
  4. For macOS: Go to System Settings > General > Software Update and install macOS Sequoia 15.5 or later
  5. For Apple TV: Go to Settings > System > Software Updates and update to tvOS 18.5
  6. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone and update to watchOS 11.5
  7. For Vision Pro: Go to Settings > General > Software Update and update to visionOS 2.5
  8. Restart the device after the update completes
Caveat Standard Apple update risks; review Apple release notes for any known issues before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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