dbcve.org
IpadosOperating system · Apple

CVE-2026-28962

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 18.7.9 / 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
This issue was addressed with improved access restrictions. This issue is fixed in Safari 26.5, iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Tahoe 26.5, visionOS 26.5. Processing maliciously crafted web content may disclose sensitive user information.

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 web content processing vulnerability in Safari and Apple OS browsers that allows sensitive user information disclosure due to insufficient access restrictions. Processing maliciously crafted web content triggers improper data exposure.

MitigationApply the vendor-supplied updates: Safari 26.5, iOS/iPadOS 18.7.9 or 26.5, macOS Tahoe 26.5, or visionOS 26.5 depending on platform. For enterprise deployments, test and deploy via patch management or MDM.

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:< 18.7.9>= 26.0, < 26.5
Iphone OsOperating system
Affected:< 18.7.9>= 26.0, < 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 the operating system version
    On iOS/iPadOS: Settings > General > About > Version. On macOS: Apple menu > About This Mac > Version. On visionOS: Settings > General > About > Version.
    Affected if The OS version falls into: iOS/iPadOS < 18.7.9 or >= 26.0 to < 26.5; macOS >= 26.0 to < 26.5; visionOS < 26.5
  2. Identify Safari version
    On iOS/iPadOS: Settings > Safari > About. On macOS: Safari > About Safari. On visionOS: Settings > Safari > About.
    Affected if Safari version is lower than 18.7.9 or between 26.0 and 26.5 (for the respective platform).
  3. Confirm Safari is the active browser
    Check if Safari is set as the default browser or is being used to browse web content.
    Affected if Safari is used as the primary browser to process web content (the vulnerability triggers when processing malicious web content).

You are affected if your device runs an affected OS version (iOS/iPadOS < 18.7.9 or 26.0-26.5, macOS 26.0-26.5, visionOS < 26.5) AND you use Safari to browse web content.

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

Apply the vendor-supplied updates: Safari 26.5, iOS/iPadOS 18.7.9 or 26.5, macOS Tahoe 26.5, or visionOS 26.5 depending on platform. For enterprise deployments, test and deploy via patch management or MDM.

Recommended fix High confidence

iOS 18.7.9 or iOS 26.5 (depending on current version branch); iPadOS 18.7.9 or iPadOS 26.5; macOS Tahoe 26.5; visionOS 26.5

  1. Identify the current installed version of iOS/iPadOS, macOS, or visionOS on the affected device
  2. For iOS/iPadOS devices on versions < 18.7.9: Upgrade to iOS 18.7.9 or iPadOS 18.7.9 via Settings > General > Software Update
  3. For iOS/iPadOS devices on versions >= 26.0 and < 26.5: Upgrade to iOS 26.5 or iPadOS 26.5 via Settings > General > Software Update
  4. For macOS devices on versions >= 26.0 and < 26.5: Upgrade to macOS Tahoe 26.5 via System Settings > General > Software Update
  5. For visionOS devices on versions < 26.5: Upgrade to visionOS 26.5 via Settings > General > Software Update
  6. After updating, verify the Safari/WebKit version reflects the fixed release
Caveat Upgrading to major OS versions (26.x) may introduce UI changes or compatibility issues with older applications

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-28962 — 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-28962 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