dbcve.org
IpadosOperating system · Apple

CVE-2026-28883

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
A use-after-free issue was addressed with improved memory management. 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, 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 confidence

A use-after-free vulnerability in Safari and Apple operating system components allows remote attackers to crash the affected process via malicious web content. The vulnerability stems from improper memory management where memory is accessed after being freed, leading to undefined behavior and process termination.

MitigationUpdate all affected Apple devices (iPhone, iPad, Mac, Apple TV, Apple Watch, Vision Pro) to the fixed versions (26.5 or later) to remediate this 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
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. Check iOS version on iPhone
    Go to Settings > General > About and look at the Version number, or run `nsurlsessiond --version` or check via iTunes/Finder
    Affected if Version is less than 26.5
  2. Check iPadOS version on iPad
    Go to Settings > General > About and look at the Version number, or run `nsurlsessiond --version`
    Affected if Version is less than 26.5
  3. Check macOS version
    Click Apple menu > About This Mac, or run `sw_vers` in Terminal
    Affected if Version is 26.0 or later but earlier than 26.5 (26.0 <= version < 26.5)
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV, or check via Finder/Console
    Affected if Version is less than 26.5
  5. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro
    Affected if Version is less than 26.5
  6. Check watchOS version
    Go to Settings > General > About on Apple Watch via iPhone Watch app, or check directly on watch
    Affected if Version is less than 26.5

You are affected if any Apple OS on your device (iOS, iPadOS, macOS 26.0+, tvOS, visionOS, or watchOS) is running a version earlier than 26.5, since the vulnerability requires processing web content through WebKit.

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 all affected Apple devices (iPhone, iPad, Mac, Apple TV, Apple Watch, Vision Pro) to the fixed versions (26.5 or later) to remediate this vulnerability.

Recommended fix High confidence

Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5

  1. Upgrade to Safari 26.5 for all affected platforms
  2. Upgrade to iOS 26.5 on iPhone devices
  3. Upgrade to iPadOS 26.5 on iPad devices
  4. Upgrade to macOS Tahoe 26.5 on Mac computers
  5. Upgrade to tvOS 26.5 on Apple TV devices
  6. Upgrade to visionOS 26.5 on Apple Vision Pro devices
  7. Upgrade to watchOS 26.5 on Apple Watch devices

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

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