dbcve.org
SafariWeb browser · Apple

CVE-2025-31204

HIGH · 8.8 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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 memory handling. This issue is fixed in Safari 18.5, iOS 18.5 and iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. Processing maliciously crafted web content may 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

Memory corruption vulnerability in WebKit affecting Safari and iOS/iPadOS/macOS/tvOS/visionOS/watchOS. Processing maliciously crafted web content leads to memory corruption, potentially allowing arbitrary code execution.

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

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

CVSS:3.1/AV:N/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. Identify your Apple device or software product
    Determine which Apple product is in use: Safari browser, iOS device (iPhone), iPadOS device (iPad), macOS computer, tvOS device (Apple TV), visionOS device (Apple Vision Pro), or watchOS (Apple Watch).
    Affected if The device runs any of these Apple products.
  2. Check Safari version on macOS
    Open Safari, go to Safari menu > About Safari. The version number displays next to Safari. On macOS, also check the macOS version via Apple menu > About This Mac.
    Affected if Safari is earlier than 18.5, or macOS is earlier than 15.5.
  3. Check iOS or iPadOS version on mobile devices
    On iPhone or iPad, go to Settings > General > About. The version number displays next to Software Version.
    Affected if iOS or iPadOS is earlier than 18.5.
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version on Apple TV.
    Affected if tvOS is earlier than 18.5.
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About on Apple Vision Pro.
    Affected if visionOS is earlier than 2.5.
  6. Check watchOS version on Apple Watch
    Open the Watch app on paired iPhone, go to My Watch > General > About, or check directly on Apple Watch via Settings > General > About.
    Affected if watchOS is earlier than 11.5.

Your environment is affected if any installed Apple product (Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS) is below the fixed version thresholds (Safari 18.5, iOS/iPadOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5) and you use Safari or any WebKit-based application to 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.5 / 11.5 / 15.5 or later
Fixed in 2.511.515.5
Interim mitigation

Apply vendor patches by updating to Safari 18.5, iOS/iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 across all affected devices.

Recommended fix High confidence

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

  1. For macOS: Go to System Settings > General > Software Update and install macOS Sequoia 15.5
  2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 18.5
  3. For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 11.5
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.5
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.5
  6. Safari will be updated automatically when macOS or iOS is updated to the fixed versions
Caveat Point upgrades typically have minimal breaking changes; review Apple release notes for any app compatibility notices

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