CVE-2025-31223
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 · uneditedThe 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 confidenceMemory corruption vulnerability in WebKit's rendering engine that can be triggered by processing maliciously crafted web content. The fix involved adding improved validation checks, likely to prevent out-of-bounds memory access or similar memory safety violations that could lead to arbitrary code execution.
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< 18.5< 18.5< 18.5< 15.5< 18.5< 2.5< 11.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check macOS versionOpen System Settings > General > About, or run 'sw_vers -productVersion' in TerminalAffected if Version is below 15.5
-
Check Safari version on macOSOpen Safari > About Safari, or check WebKit version in Safari's version informationAffected if Safari version is below 18.5 (corresponds to WebKit vulnerable version)
-
Check iOS or iPadOS versionOpen Settings > General > About on the deviceAffected if Version is below 18.5
-
Check tvOS, watchOS, or visionOS versionOpen Settings > General > About on the Apple TV, Apple Watch, or Apple Vision ProAffected if tvOS version is below 18.5, watchOS version is below 11.5, or visionOS version is below 2.5
A user is affected if any of their Apple operating systems or Safari browsers are running a version lower than the fixed releases (macOS 15.5, iOS/iPadOS/tvOS/watchOS/visionOS 18.5 or 11.5, Safari 18.5).
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.511.515.5
Apply vendor-supplied security updates: update Safari to 18.5, iOS/iPadOS to 18.5, macOS to Sequoia 15.5, tvOS to 18.5, visionOS to 2.5, and watchOS to 11.5.
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 applicable to your device)
- Check current version: On iOS/iPadOS go to Settings > General > About, on macOS go to Apple menu > About This Mac, on tvOS/watchOS/visionOS go to Settings > General > About, or in Safari go to Safari > About Safari
- Update iOS/iPadOS: Go to Settings > General > Software Update and install iOS/iPadOS 18.5 or later
- Update macOS: Go to Apple menu > About This Mac > Software Update and install macOS Sequoia 15.5 or later
- Update Safari: Safari 18.5 is included with the OS updates above; for separate Safari updates use Software Update
- Update tvOS: Go to Settings > General > Software Update and install tvOS 18.5 or later
- Update watchOS: Go to Settings > General > Software Update on iPhone paired with Apple Watch, or on Apple Watch go to Settings > General > Software Update and install watchOS 11.5 or later
- Update visionOS: Go to Settings > General > Software Update and install visionOS 2.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31223 — 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- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- bugzilla.redhat.com
- security.access.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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