dbcve.org
IpadosOperating system · Apple

CVE-2026-28913

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, 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

A memory handling vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected process crash. This affects Safari 26.4 and earlier, along with iOS, iPadOS, macOS, tvOS, and watchOS versions prior to 26.5. The fix involves improved memory handling in the browser engine.

MitigationApply vendor-supplied updates to patch all affected Apple products (Safari, iOS, iPadOS, macOS, tvOS, watchOS) to version 26.5 or later. Until patched, avoid visiting untrusted websites.

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
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 the Apple product
    Determine which Apple platform is running: macOS, iOS, iPadOS, tvOS, or watchOS. On macOS, also note if Safari browser is in use.
    Affected if Any Apple device running Safari or a WebKit-based browser on an affected platform.
  2. Check macOS version
    Open Terminal and run: sw_vers -productVersion. Compare the output to the affected range 26.0 to 26.4.x.
    Affected if Version is 26.0, 26.1, 26.2, 26.3, or 26.4 (any minor version).
  3. Check iOS or iPadOS version
    Go to Settings > General > About on the device. Note the version number.
    Affected if Version is earlier than 26.5 (e.g., 26.4, 26.3, etc.).
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV.
    Affected if Version is earlier than 26.5.
  5. Check watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About, or check directly on Apple Watch via Settings > General > About.
    Affected if Version is earlier than 26.5.
  6. Check Safari version on macOS
    Open Safari, go to Safari > About Safari. The version should match the macOS version for bundled Safari.
    Affected if Safari version corresponds to an affected macOS version (26.0-26.4.x).

The environment is affected if running macOS 26.0 through 26.4.x, or any version of iOS, iPadOS, tvOS, or watchOS earlier than 26.5, especially when using Safari or other WebKit-based browsers.

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

Apply vendor-supplied updates to patch all affected Apple products (Safari, iOS, iPadOS, macOS, tvOS, watchOS) to version 26.5 or later. Until patched, avoid visiting untrusted websites.

Recommended fix High confidence

iOS 26.5 / iPadOS 26.5 / macOS Tahoe 26.5 / tvOS 26.5 / watchOS 26.5 / Safari 26.5

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, or Apple Watch)
  2. On iPhone/iPad: Go to Settings > General > Software Update and install iOS 26.5 or iPadOS 26.5
  3. On Mac: Go to System Settings > General > Software Update and install macOS Tahoe 26.5
  4. On Apple TV: Go to Settings > System > Software Updates and install tvOS 26.5
  5. On Apple Watch: Go to Settings > General > Software Update and install watchOS 26.5
  6. Ensure Safari is updated to version 26.5 as part of the OS update
Caveat Standard OS update risks apply; back up data before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
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,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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