SafariWeb browser · Apple
CVE-2026-43704
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 use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26.5.2, 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 web extension may be able to cause an unexpected process 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 · high confidenceA use-after-free vulnerability in WebKit allows a malicious web extension to cause an unexpected process crash due to improper memory management. The vulnerability exists in multiple Apple operating systems and was addressed with improved memory management in the specified version updates.
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.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOSOpen Safari, click Safari menu, select 'About Safari', and note the version number displayedAffected if Version shown is earlier than 26.5.2
-
Check iOS version on iPhoneOpen Settings app, tap General, tap About, and note the iOS version numberAffected if Version shown is earlier than 26.5.2
-
Check iPadOS version on iPadOpen Settings app, tap General, tap About, and note the iPadOS version numberAffected if Version shown is earlier than 26.5.2
-
Check macOS system versionClick Apple menu, select 'About This Mac', and note the macOS version name and numberAffected if Running a macOS version that ships with Safari earlier than 26.5.2
If any Apple device (Safari, iPhone, iPad, or Mac) runs a version earlier than 26.5.2 AND uses web extensions, the environment is affected by this CVE.
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
Apply vendor-supplied patches: update Safari to 26.5.2, iOS/iPadOS to 26.5.2, macOS Tahoe to 26.5.2, tvOS to 26.6, visionOS to 26.6, and watchOS to 26.6.
Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, macOS Tahoe 26.5.2
- Identify the affected Apple device: Safari on macOS, iOS, iPadOS, or other Apple platforms
- For macOS users: Update to macOS 26.5.2 (Tahoe) via System Settings > Software Update
- For iOS users: Update to iOS 26.5.2 via Settings > General > Software Update
- For iPadOS users: Update to iPadOS 26.5.2 via Settings > General > Software Update
- For Safari users on older macOS: Update Safari to version 26.5.2 through the macOS Software Update
- Verify the update was installed successfully by checking the OS/Safari version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43704 — 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-43704 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