SafariWeb browser · Apple
CVE-2026-43735
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 · uneditedThe issue was addressed with improved checks. This issue is fixed in Safari 26.5.2, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.5.2 and iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, watchOS 26.6. A malicious website may exfiltrate data cross-origin.
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 confidenceCross-origin data exfiltration vulnerability in WebKit (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allowing a malicious website to steal data from other origins. The fix implements improved validation checks to prevent unauthorized cross-origin data access.
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
SafariWeb browser
< 26.5.2< 26.5.2< 26.5.2>= 26.0, < 26.5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the browser or platformDetermine if you are using Safari on macOS, iOS, or iPadOS, or any WebKit-based browser. Check the application name and the OS it runs on.Affected if The browser is Safari or another WebKit-based browser on Apple platforms.
-
Check Safari version on macOSOpen Safari, go to Safari Menu > About Safari. The version number is displayed next to Safari.Affected if The version shown is 26.0 through 26.5.1 (any version >= 26.0 but < 26.5.2).
-
Check Safari version on iOS or iPadOSOpen Settings > Safari > About. The version is displayed under the Safari name.Affected if The version shown is < 26.5.2.
-
Check if using WebKit-based third-party browsersIdentify any third-party browsers installed that use WebKit (common on iOS). Check their version in the App Store or app settings.Affected if A WebKit-based browser is installed with a version corresponding to the affected WebKit build.
You are affected if Safari or any WebKit-based browser on macOS, iOS, or iPadOS is running a version earlier than 26.5.2 (or 26.0 to 26.5.1 on macOS).
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 · scoped26.5.2
Update all affected Apple devices to the fixed versions: Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, or watchOS 26.6.
Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, macOS Tahoe 26.5.2
- For macOS: Open System Settings > General > Software Update and install the macOS Tahoe 26.5.2 update
- For iOS: Go to Settings > General > Software Update and install iOS 26.5.2
- For iPadOS: Go to Settings > General > Software Update and install iPadOS 26.5.2
- For Safari on older macOS: Open the App Store or use Software Update to install Safari 26.5.2
- After updating, restart all affected devices to ensure the security fix is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- 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-43735 — 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-43735 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