dbcve.org
IpadosOperating system · Apple

CVE-2026-28947

HIGH · 8.8 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 26.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 18.7.10 and iPadOS 18.7.10, 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 Safari 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

Use-after-free vulnerability in Safari's WebKit rendering engine that is triggered when processing maliciously crafted web content, potentially leading to unexpected browser crash. The vulnerability stems from improper memory management during web content processing.

MitigationUpdate affected Apple devices to Safari 26.5, iOS 18.7.10/iOS 26.5, iPadOS 18.7.10/iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, or watchOS 26.5 respectively.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Check iOS version
    On iPhone, go to Settings > General > About and look at the 'Software Version' field. On iPad, same path. Alternatively, connect to computer and check via iTunes/Finder or use ideviceinfo command-line tool.
    Affected if Version is lower than 26.5
  2. Check iPadOS version
    Go to Settings > General > About on the iPad and note the software version number.
    Affected if Version is lower than 26.5
  3. Check macOS version
    Click the Apple menu > About This Mac. The version number appears below the macOS name (e.g., '26.4' or '26.3').
    Affected if Version is 26.0 through 26.4 (inclusive)
  4. Check Safari version
    Open Safari, then Safari > About Safari. The version number displays in the pop-up window.
    Affected if Version is lower than 26.5
  5. Check tvOS, visionOS, or watchOS version
    On Apple TV: Settings > General > About > Version. On Apple Watch: Settings > General > About. On Vision Pro: Settings > General > About.
    Affected if Version is lower than 26.5 on any of these platforms

You are affected if any device runs iOS, iPadOS, macOS 26.0-26.4, tvOS, visionOS, or watchOS versions below 26.5, or uses Safari versions below 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 affected Apple devices to Safari 26.5, iOS 18.7.10/iOS 26.5, iPadOS 18.7.10/iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, or watchOS 26.5 respectively.

Recommended fix High confidence

Upgrade to Safari 26.5, iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, or watchOS 26.5 as appropriate for each device

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 26.5 / iPadOS 26.5
  2. For Mac: Go to System Settings > General > Software Update and install macOS Tahoe 26.5, then update Safari to 26.5
  3. For Apple TV: Go to Settings > System > Software Updates and install tvOS 26.5
  4. For Apple Watch: Go to Settings > General > Software Update on the watch or via iPhone Watch app and install watchOS 26.5
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26.5
  6. Alternatively, connect device to power and Wi-Fi and say "Hey Siri, install the latest software update" to trigger automatic update check
Caveat Standard minor version updates typically have minimal breaking changes; ensure backup of important 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
  • 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-28947 — 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-28947 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