dbcve.org
IpadosOperating system · Apple

CVE-2026-28905

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 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 26.5 and iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 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 confidence

A memory handling vulnerability in WebKit (the rendering engine used by Safari and Apple's mobile operating systems) that can be triggered by processing maliciously crafted web content, leading to an unexpected process crash. The issue was addressed with improved memory handling in the patched versions.

MitigationUpdate to Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5 or later versions to remediate the 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
IpadosOperating system
Affected:< 26.5
Iphone OsOperating system
Affected:< 26.5
macOSOperating system
Affected:>= 26.0, < 26.5
TvosOperating system
Affected:< 26.5
VisionosOperating 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 the operating system product
    Check which Apple platform is in use: iOS (iPhone), iPadOS (iPad), macOS (Mac), tvOS (Apple TV), or visionOS (Vision Pro). This determines which version range applies.
    Affected if The device is running any of the affected Apple operating systems.
  2. Check iOS or iPadOS version on mobile devices
    On iPhone or iPad, go to Settings > General > About and note the Version number. Compare it to the affected range: iOS < 26.5, iPadOS < 26.5.
    Affected if The version number is less than 26.5 for iOS or iPadOS.
  3. Check macOS version on Mac computers
    On Mac, go to System Settings > About (or Apple menu > About This Mac) and note the macOS version number. Compare to the affected range: >= 26.0 and < 26.5.
    Affected if The macOS version is 26.0, 26.1, 26.2, 26.3, or 26.4 (any version >= 26.0 but below 26.5).
  4. Check tvOS version on Apple TV
    On Apple TV, go to Settings > General > About > Version and note the tvOS version. Compare to the affected range: tvOS < 26.5.
    Affected if The tvOS version is less than 26.5.
  5. Check visionOS version on Vision Pro
    On Vision Pro, go to Settings > General > About and note the visionOS version. Compare to the affected range: visionOS < 26.5.
    Affected if The visionOS version is less than 26.5.

The environment is affected if the installed Apple operating system version falls within any of the specified vulnerable ranges: iOS < 26.5, iPadOS < 26.5, macOS >= 26.0 and < 26.5, tvOS < 26.5, or visionOS < 26.5.

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

Update to Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5 or later versions to remediate the vulnerability.

Recommended fix High confidence

iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5 (or Safari 26.5)

  1. For iPhone: Go to Settings > General > Software Update and install iOS 26.5
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 26.5
  3. For Mac: Go to System Settings > General > Software Update and install macOS Tahoe 26.5
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 26.5
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26.5
  6. Alternatively, ensure Safari is updated to version 26.5 through the macOS Software Update mechanism

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

Fix this in Ipados 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-2026-28905 — 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-28905 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