CVE-2026-43660
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 · uneditedA validation issue was addressed with improved logic. 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 · high confidenceThis is a Content Security Policy (CSP) bypass vulnerability in WebKit/Safari. A validation issue allows maliciously crafted web content to prevent CSP from being properly enforced, potentially enabling cross-site scripting (XSS) attacks or other code injection attacks that CSP is designed to mitigate.
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< 18.7.9>= 26.0, < 26.5< 18.7.9>= 26.0, < 26.5>= 26.0, < 26.5< 26.5< 26.5< 26.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS/iPadOS Safari versionOpen Settings > General > About > Version, or open Safari > Settings (or Preferences) > About. Record the version number shown.Affected if Version is below 18.7.9 OR version is 26.0 to 26.5 (not inclusive of 26.5)
-
Check macOS Safari versionOpen Safari > About Safari, or check System Information app under Software > Safari. Record the version number.Affected if Version is 26.0 to 26.5 (not inclusive of 26.5)
-
Check tvOS versionOpen Settings > General > About > Version. Record the build number or version.Affected if Version is below 26.5
-
Check visionOS versionOpen Settings > General > About > Version. Record the build number or version.Affected if Version is below 26.5
-
Check watchOS versionOpen Settings > General > About > Version on the Apple Watch, or open the Watch app on iPhone and check My Watch > General > About. Record the version number.Affected if Version is below 26.5
You are affected if any Apple device runs a WebKit-based browser (Safari) with a version that falls within the vulnerable ranges: iOS/iPadOS below 18.7.9 or between 26.0 and 26.5, macOS Safari between 26.0 and 26.5, or tvOS/visionOS/watchOS below 26.5.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.7.926.5
Apply the vendor-supplied updates: 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. Ensure all affected Apple devices and browsers are updated to these versions or later.
iOS 18.7.9 or iOS 26.5 / iPadOS 18.7.9 or iPadOS 26.5, macOS 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5, Safari 26.5
- Open Settings app on iPhone or iPad, go to General > Software Update, and install iOS/iPadOS 18.7.9 (or iOS/iPadOS 26.5 for newer devices)
- On Mac, open System Settings > General > Software Update and install macOS 26.5
- On Apple TV, go to Settings > System > Software Updates and install tvOS 26.5
- On Apple Vision Pro, go to Settings > General > Software Update and install visionOS 26.5
- On Apple Watch, open the Watch app on iPhone, go to General > Software Update and install watchOS 26.5
- For Safari, updating the OS to the fixed versions will automatically include Safari 26.5
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43660 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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