CVE-2025-31277
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 memory handling. This issue is fixed in Safari 18.6, iOS 18.6 and iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6. 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 confidenceA memory corruption vulnerability in WebKit allows processing of maliciously crafted web content to trigger memory corruption. The issue stems from improper memory handling and affects Safari and WebKit-based browsers across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.
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.6= 6.0= 7.0= 8.0= 9.0= 8.2= 8.4= 8.6= 7.0= 8.4= 8.6= 9.4= 8.6= 8.8= 8.6= 8.8= 9.0= 9.2< 18.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOSOpen Safari, then go to Safari > About Safari (or press Cmd+comma) and note the version number displayedAffected if Version is earlier than 18.6 (for example, 18.5.x or earlier)
-
Check iOS version on iPhone or iPadOn the device, go to Settings > General > About and note the version number under Software VersionAffected if Version is earlier than 18.6 (for example, 18.5.x or earlier)
-
Check iPadOS version on iPadOn the device, go to Settings > General > About and note the version number under Software VersionAffected if Version is earlier than 18.6 (for example, 18.5.x or earlier)
-
Check Red Hat Enterprise Linux versionRun the command 'cat /etc/redhat-release' in a terminal to display the installed RHEL versionAffected if Version exactly matches 6.0, 7.0, 8.0, 9.0, 8.2, 8.4, 8.6, 8.8, 9.2, or 9.4 as listed in the affected versions
You are affected if you run any Safari version before 18.6, any iOS/iPadOS version before 18.6, or a Red Hat Enterprise Linux version that exactly matches one of the listed affected versions.
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 · scoped18.6
Apply the vendor-supplied updates: Safari 18.6, iOS/iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, and watchOS 11.6.
iOS 18.6 / iPadOS 18.6 / Safari 18.6 / macOS Sequoia 15.6 / tvOS 18.6 / visionOS 2.6 / watchOS 11.6
- For iOS devices: Upgrade to iOS 18.6 or later via Settings > General > Software Update
- For iPadOS devices: Upgrade to iPadOS 18.6 or later via Settings > General > Software Update
- For Safari: Upgrade to Safari 18.6 (included with macOS Sequoia 15.6 or via standalone update for earlier macOS)
- For macOS: Upgrade to macOS Sequoia 15.6 or later via System Settings > General > Software Update
- For Apple TV: Upgrade to tvOS 18.6 or later via Settings > System > Software Updates
- For Apple Watch: Upgrade to watchOS 11.6 or later via the Watch app on iPhone
- For Apple Vision Pro: Upgrade to visionOS 2.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-31277 — 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
- 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
- cloud.google.com
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31277 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