CVE-2026-28847
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 26.5, iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5. Processing maliciously crafted web content may lead to an unexpected process 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 · high confidenceA memory handling vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected process crash. The vulnerability has a CVSS 8.8 (HIGH) indicating potential for exploitation beyond denial of service. Affected products include Safari 26.5, iOS 18.7.9/26.5, iPadOS 18.7.9/26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, and watchOS 26.5.
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.7.9>= 26.0, < 26.5< 18.7.9>= 26.0, < 26.5>= 26.0, < 26.5< 26.5< 26.5< 26.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
- 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 iOS version on iPhone or iPadGo to Settings > General > About > Version to view the installed iOS versionAffected if Version is below 18.7.9 OR between 26.0 and 26.5 (excluding 26.5)
-
Check macOS versionGo to Apple menu > About This Mac to view the installed macOS versionAffected if Version is between 26.0 and 26.5 (excluding 26.5)
-
Check tvOS versionGo to Settings > General > About > Version on Apple TVAffected if Version is below 26.5
-
Check visionOS versionGo to Settings > General > About on Apple Vision ProAffected if Version is below 26.5
-
Check watchOS versionGo to Settings > General > About on Apple WatchAffected if Version is below 26.5
-
Confirm WebKit browser usageVerify Safari or any WebKit-based browser is in use, as this vulnerability is triggered when processing web contentAffected if A WebKit browser is actively used on an affected OS version
You are affected if your device runs any of the listed Apple OS versions within the affected ranges AND uses a WebKit-based browser that could process malicious web content.
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.7.926.5
Apply vendor-supplied patches by updating all affected Apple devices to the fixed versions listed in the security advisory. Prioritize internet-facing systems and those processing untrusted web content.
iOS 18.7.9, iPadOS 18.7.9, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, or watchOS 26.5 (depending on device type)
- Identify the affected Apple device type (iPhone, iPad, Mac, Apple TV, Apple Watch, or Apple Vision Pro)
- Check the current OS version on the device (Settings > General > About on iOS/iPadOS, System Settings > About on macOS, Settings > General on tvOS/watchOS/visionOS)
- For iPhone/iPad: Navigate to Settings > General > Software Update and install iOS 18.7.9 or iOS/iPadOS 26.5 depending on which major version branch the device is on
- For Mac: Navigate to System Settings > General > Software Update and install macOS Tahoe 26.5
- For Apple TV: Go to Settings > General > Software Update and install tvOS 26.5
- For Apple Watch: Go to Settings > General > Software Update and install watchOS 26.5
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26.5
- Verify the update was successfully installed by checking the OS version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28847 — 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
- support.apple.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
- www.zerodayinitiative.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28847 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