dbcve.org
IpadosOperating system · Apple

CVE-2026-28907

HIGH · 8.1 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 18.7.9 / 26.5 or later.
See remediation →
88/100
Remediation priority · High
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
The issue was addressed with improved input validation. 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, tvOS 26.5, visionOS 26.5, watchOS 26.5. Processing maliciously crafted web content may prevent Content Security Policy from being enforced.

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

This is a Content Security Policy (CSP) bypass vulnerability in Apple Safari and related platforms. Processing maliciously crafted web content can prevent CSP from being enforced due to improper input validation, potentially allowing cross-site scripting attacks or data exfiltration.

MitigationApply the available vendor patches for affected Apple products: Safari 26.5, iOS 18.7.9/iPadOS 18.7.9, iOS 26.5/iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, and watchOS 26.5.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 your Apple device and operating system version
    On iPhone/iPad: Settings > General > About > Software Version. On Mac: Apple menu > About This Mac > macOS version. On Apple Watch: Settings > General > About > Watch OS version. On Apple TV: Settings > General > About > Version. On Apple Vision Pro: Settings > General > About > visionOS version.
    Affected if The OS version falls within any of these ranges: iOS/iPadOS < 18.7.9 OR >= 26.0 to < 26.5; macOS >= 26.0 to < 26.5; tvOS < 26.5; visionOS < 26.5; watchOS < 26.5
  2. Confirm Safari or WebKit-based browser usage
    Check if Safari is the default browser (iOS: Settings > Safari; macOS: Safari > Settings > General > Default browser). Note that any WebKit-based browser on Apple platforms uses the same underlying rendering engine vulnerable to this CSP bypass.
    Affected if Safari or any WebKit-based browser is used as the primary browser on an affected OS version
  3. Verify CSP headers are in use in your web applications
    If you manage web applications, inspect the HTTP response headers for Content-Security-Policy directives. Use browser DevTools (Network tab) or command-line tools like 'curl -I <url>' to examine response headers.
    Affected if Content-Security-Policy headers are deployed but may not be enforced due to this vulnerability, meaning attackers could potentially bypass your CSP protections

You are affected if your Apple device runs any OS version listed as vulnerable (iOS/iPadOS < 18.7.9 or 26.0-26.5, macOS 26.0-26.5, tvOS/visionOS/watchOS < 26.5) and you use Safari or WebKit-based browsers to process untrusted 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 available vendor patches for affected Apple products: Safari 26.5, iOS 18.7.9/iPadOS 18.7.9, iOS 26.5/iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, and watchOS 26.5.

Recommended fix High confidence

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

  1. For iPhone/iPad users: Update to iOS 18.7.9 or iOS 26.5 / iPadOS 18.7.9 or iPadOS 26.5 via Settings > General > Software Update
  2. For macOS users: Update to macOS Tahoe 26.5 via System Settings > General > Software Update
  3. For tvOS users: Update to tvOS 26.5 via Settings > General > Apple TV Software Update
  4. For visionOS users: Update to visionOS 26.5 via Settings > General > Software Update
  5. For watchOS users: Update to watchOS 26.5 via the Watch app on iPhone > General > Software Update
  6. Alternatively for Safari-based attacks: Update Safari to version 26.5

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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