dbcve.org
IpadosOperating system · Apple

CVE-2026-28904

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 18.7.9 / 26.5 or later.
See remediation →
84/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 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 · moderate confidence

This is a WebKit memory handling vulnerability in Apple's browser engine. Processing maliciously crafted web content triggers improper memory management, leading to an unexpected process crash (denial of service). The fix involves improved memory handling in the affected Safari and WebKit components.

MitigationUpdate to the patched versions: Safari 26.5, 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.

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
IpadosOperating system
Affected:< 18.7.9>= 26.0, < 26.5
Iphone OsOperating system
Affected:< 18.7.9>= 26.0, < 26.5
macOSOperating system
Affected:>= 26.0, < 26.5
TvosOperating system
Affected:< 26.5
VisionosOperating system
Affected:< 26.5
WatchosOperating system
Affected:< 26.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
High
Integrity
None
Availability
None

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

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 WebKit-based applications in use
    Look for Safari or any third-party browsers (Chrome, Firefox, etc. on iOS all use WebKit) installed on the device
    Affected if Any WebKit-based browser is used and its version falls within the affected ranges
  2. Check Safari version on iOS/iPadOS
    Go to Settings > Safari > About, or check via iTunes/Finder when device is connected
    Affected if Safari version is below 18.7.9, or between 26.0 and 26.5 (exclusive)
  3. Check iOS or iPadOS version
    Go to Settings > General > About and note the version number
    Affected if iOS/iPadOS version is below 18.7.9, or between 26.0 and 26.5 (exclusive)
  4. Check Safari or WebKit version on macOS
    Open Safari, go to Safari > About Safari, or check system profiler for WebKit version
    Affected if macOS version is between 26.0 and 26.5 (exclusive), meaning Safari/WebKit is vulnerable
  5. Check tvOS, visionOS, or watchOS version
    Go to Settings > General > About on the Apple TV, Vision Pro, or Apple Watch companion app on iPhone
    Affected if tvOS version is below 26.5, visionOS version is below 26.5, or watchOS version is below 26.5

A user is affected if they run any Safari or WebKit-based application on a vulnerable iOS, iPadOS, macOS, tvOS, visionOS, or watchOS version, and they could potentially encounter malicious web content that triggers the crash.

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 18.7.9 / 26.5 or later
Fixed in 18.7.926.5
Interim mitigation

Update to the patched versions: Safari 26.5, 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.

Recommended fix High confidence

iOS/iPadOS 18.7.9 or 26.5 (depending on current version); macOS Tahoe 26.5; tvOS 26.5; watchOS 26.5; visionOS 26.5

  1. Open Settings > General > Software Update on iPhone/iPad
  2. Ensure the device is connected to Wi-Fi and has sufficient battery
  3. Download and install iOS 18.7.9 (for iOS < 18.7.9) or iOS 26.5 (for iOS 26.0-26.4)
  4. Restart the device after update completes
  5. For macOS: Open System Settings > General > Software Update
  6. Download and install macOS Tahoe 26.5 if running 26.0-26.4
  7. For tvOS/watchOS/visionOS: Go to Settings > General > Software Update on the respective device
  8. Install the available 26.5 update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28904 — 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-2026-28904 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