dbcve.org
SafariWeb browser · Apple

CVE-2025-31215

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
The issue was addressed with improved checks. 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. Processing maliciously crafted web content may lead to an unexpected process 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 vulnerability in WebKit allows processing maliciously crafted web content to cause an unexpected process crash. The fix implemented improved checks to prevent this condition.

MitigationApply the vendor-supplied updates for Safari, iOS, iPadOS, macOS, tvOS, visionOS, and watchOS to the versions specified in the fixed-in list.

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.5
IpadosOperating system
Affected:< 17.7.7>= 18.0, < 18.5
Iphone OsOperating system
Affected:< 18.5
macOSOperating system
Affected:< 15.5
TvosOperating system
Affected:< 18.5
VisionosOperating system
Affected:< 2.5
WatchosOperating system
Affected:< 11.5

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 the product and version
    Check the OS or Safari version: On macOS, go to Safari > About Safari. On iOS/iPadOS, go to Settings > General > About. On tvOS/visionOS/watchOS, go to Settings > General > About.
    Affected if The product is any of Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS with a version lower than the fixed versions.
  2. Compare macOS version to affected range
    Run 'sw_vers' in Terminal or check System Settings > General > About. Look for the macOS version number (e.g., 15.4, 15.3).
    Affected if macOS version is below 15.5.
  3. Compare iOS/iPadOS version to affected range
    Go to Settings > General > About on the device and note the iOS/iPadOS version number.
    Affected if iOS/iPadOS version is below 17.7.7 OR between 18.0 and 18.4.x.
  4. Compare Safari version to affected range
    Open Safari > About Safari on macOS, or check the App Store for Safari updates on iOS/iPadOS.
    Affected if Safari version is below 18.5.
  5. Verify WebKit is accessible for exploitation
    Confirm the device has a web browser or app that uses WebKit rendering engine enabled and functional.
    Affected if WebKit is available and can process web content - this is required for the malicious content to trigger the crash.

A user is affected if they run any Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS version below the fixed thresholds (18.5 for Safari/iOS/iPadOS/tvOS/visionOS, 15.5 for macOS, 11.5 for watchOS, or 17.7.7 for iOS/iPadOS 17.x) and have WebKit available to process 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.5 / 11.5 / 15.5 or later
Fixed in 2.511.515.5
Interim mitigation

Apply the vendor-supplied updates for Safari, iOS, iPadOS, macOS, tvOS, visionOS, and watchOS to the versions specified in the fixed-in list.

Recommended fix High confidence

Safari 18.5, iOS 18.5, iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
  2. Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Settings > General > About on macOS)
  3. For iOS/iPadOS devices: Navigate to Settings > General > Software Update and install the available security update
  4. For macOS: Navigate to System Settings > General > Software Update and install the available security update
  5. For tvOS: Navigate to Settings > General > Software Update and install the available security update
  6. For visionOS: Navigate to Settings > General > Software Update and install the available security update
  7. For watchOS: Navigate to Settings > General > Software Update and install the available security update
  8. For Safari on older macOS: Update Safari via macOS software update or App Store updates

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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