SafariWeb browser · Apple

CVE-2025-31238

HIGH · 7.3 CVSS v3.1 Published 2025-05-12
Fix available
A fix is available. Upgrade to 2.5 / 11.5 or later.
See remediation →
82/100
Remediation priority · High
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 checks. 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 · moderate confidence

Memory corruption vulnerability in WebKit affecting Safari and iOS/iPadOS/macOS/tvOS/visionOS/watchOS. Processing maliciously crafted web content can trigger memory corruption, likely due to improper bounds checking or memory management in WebKit's rendering engine.

MitigationUpdate affected Apple devices to Safari 18.5, iOS/iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 to receive the improved checks that address this vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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.5
  2. Check Safari version on iOS/iPadOS
    Open Settings app, scroll to Safari, tap it, scroll to bottom and tap About. Note the version number.
    Affected if Version is earlier than 18.5
  3. Check macOS version
    Click Apple menu > About This Mac. Note the version number under macOS name.
    Affected if Version is earlier than 15.5 ( Sequoia )
  4. Check iOS or iPadOS version
    Open Settings app, tap General > About. Note the version number.
    Affected if Version is earlier than 18.5
  5. Check tvOS version
    Open Settings app, go to General > About. Note the version number.
    Affected if Version is earlier than 18.5
  6. Check visionOS version
    Open Settings app, go to General > About. Note the version number.
    Affected if Version is earlier than 2.5

You are affected if any WebKit-based browser (Safari) or Apple OS version listed above is running a version lower than the fixed release for your product.

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

Update affected Apple devices to Safari 18.5, iOS/iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 to receive the improved checks that address this vulnerability.

Recommended fix High confidence

Upgrade to Safari 18.5, iOS 18.5, iPadOS 18.5, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, or watchOS 11.5 as appropriate for the device

  1. Identify the affected Apple device type (iPhone, iPad, Mac, Apple Watch, Apple TV, or Vision Pro)
  2. Check current OS version in Settings > General > About (iOS/iPadOS/macOS) or Settings > General (tvOS/watchOS/visionOS)
  3. For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS/iPadOS 18.5
  4. For Mac: Go to System Settings > General > Software Update and upgrade to macOS Sequoia 15.5
  5. For Apple TV: Go to Settings > General > Software Update and upgrade to tvOS 18.5
  6. For Apple Watch: Open Watch app on iPhone, go to General > Software Update and upgrade to watchOS 11.5
  7. For Vision Pro: Go to Settings > General > Software Update and upgrade to visionOS 2.5
  8. Safari will be updated automatically through macOS Sequoia 15.5 or as Safari 18.5
Caveat Standard OS upgrade considerations apply - review app compatibility before updating

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