dbcve.org
IpadosOperating system · Apple

CVE-2026-28944

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, 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 · moderate confidence

A memory handling vulnerability in WebKit affects Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, and visionOS 26.5. Processing maliciously crafted web content triggers improper memory operations leading to an unexpected process crash. While the primary impact described is denial-of-service, memory handling flaws can potentially be escalated to more severe outcomes.

MitigationApply vendor-supplied updates: Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, and visionOS 26.5 contain the fix. Deploy these versions organization-wide to all affected Apple devices.

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
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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify iOS or iPadOS version
    On the device, go to Settings > General > About > Version. Alternatively, use an MDM solution, Apple Configurator, or check via mobile device management console.
    Affected if Version is less than 26.5
  2. Identify macOS version
    Open System Settings > About > macOS, or run 'sw_vers' in Terminal, or use 'system_profiler SPSoftwareDataType'.
    Affected if Version is 26.0 or higher but lower than 26.5 (26.0.x where x is any subversion below 26.5)
  3. Identify visionOS version
    On the Vision Pro device, go to Settings > About > Version. Check via device management tools if deployed in an enterprise environment.
    Affected if Version is less than 26.5
  4. Confirm WebKit is exposed
    Verify that Safari or any web browser using the system WebKit engine is in use. This is the default on Apple platforms - no configuration change needed.
    Affected if Any web browser based on WebKit is accessible on the device (this is the default state)

The environment is affected if any Apple device runs iOS, iPadOS, macOS 26.0-26.4, or visionOS with a version number lower than 26.5, and WebKit-based browsing is accessible.

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: Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, and visionOS 26.5 contain the fix. Deploy these versions organization-wide to all affected Apple devices.

Recommended fix High confidence

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

  1. Update iPadOS to version 26.5 or later via Settings > General > Software Update
  2. Update iPhone (iOS) to version 26.5 or later via Settings > General > Software Update
  3. Update macOS Tahoe to version 26.5 or later via System Preferences > Software Update
  4. Update visionOS to version 26.5 or later via Settings > General > Software Update
  5. Ensure Safari is also updated to version 26.5 as part of the iOS/iPadOS/macOS updates

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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