SafariWeb browser · Apple

CVE-2025-31217

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 input validation. 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 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

This is a WebKit vulnerability in Safari and Apple's ecosystem products. Processing maliciously crafted web content triggers improper input validation, leading to an unexpected Safari crash (denial of service). The fix implements improved input validation to prevent the crash condition.

MitigationApply vendor patches by updating all affected Apple devices to Safari 18.5, iOS/iPadOS 18.5 or 17.7.7, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate.

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. Check Safari version on macOS
    Open Safari, go to Safari > About Safari. The version number appears in the window.
    Affected if Version is earlier than 18.5
  2. Check macOS version
    Click Apple menu > About This Mac. The version number displays below the macOS name.
    Affected if macOS version is earlier than 15.5 (Sequoia)
  3. Check iOS or iPadOS version on iPhone or iPad
    Go to Settings > General > About. The version number displays next to Software Version.
    Affected if iOS/iPadOS version is earlier than 17.7.7 OR is 18.0 to 18.4 (vulnerable range)
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version.
    Affected if tvOS version is earlier than 18.5
  5. Check watchOS version on Apple Watch
    On iPhone, open Watch app, go to My Watch > General > About. Or on watch, go to Settings > General > About.
    Affected if watchOS version is earlier than 11.5
  6. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About > Software Version.
    Affected if visionOS version is earlier than 2.5

If any Apple device runs a browser or WebKit-based application and the OS/browser version falls within the vulnerable ranges listed, the environment is affected by this denial-of-service vulnerability.

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 vendor patches by updating all affected Apple devices to Safari 18.5, iOS/iPadOS 18.5 or 17.7.7, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate.

Recommended fix High confidence

Safari 18.5, iOS 18.5, iPadOS 18.5 (or 17.7.7 for iPadOS 17), macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5

  1. Identify the affected Apple device type (iPhone, iPad, Mac, Apple Watch, Apple TV, Vision Pro)
  2. Determine the current installed version from Settings > General > About (iOS/iPadOS), System Settings > General > About (macOS), or Settings app on other devices
  3. For iPhone/iPad: Navigate to Settings > General > Software Update and install the available update
  4. For macOS: Go to System Settings > General > Software Update and install the available update
  5. For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update
  6. For Apple TV: Go to Settings > System > Software Updates > Update Software
  7. For Vision Pro: Go to Settings > General > Software Update
  8. After updating, verify the version matches or exceeds the fixed release for your device
Caveat Standard minor version updates - review Apple release notes for any behavioral changes; backup data before updating as standard precaution

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-31217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-31217 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