SafariWeb browser · Apple
CVE-2026-43712
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 memory handling. 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. Processing maliciously crafted web content may lead to 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 · moderate confidenceMemory handling vulnerability in WebKit/Safari allowing remote crash via malicious web content. The vulnerability stems from improper memory management when processing crafted web content, leading to an unexpected process crash. Affects Safari, iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Identify the installed Apple productDetermine whether the device runs Safari, iOS, iPadOS, or macOS. On macOS, check System Settings > General > About to see the macOS version.Affected if The device runs any of the affected Apple platforms (Safari, iOS, iPadOS, macOS).
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. Note the version number displayed.Affected if Safari version is earlier than 26.5.2 (e.g., 26.5.1, 26.5.0, or any earlier version).
-
Check iOS or iPadOS version on iPhone or iPadOpen Settings > General > About. Note the version number next to Software Version.Affected if iOS or iPadOS version is earlier than 26.5.2.
-
Check macOS version if not using SafariOpen System Settings > General > About. Note the macOS version number displayed (e.g., 26.0, 26.1, 26.5.1).Affected if macOS version is 26.0 through 26.5.1 (inclusive), which includes the vulnerable WebKit component.
A device is affected if it runs Safari, iOS, iPadOS, or macOS with a version lower than 26.5.2, or macOS 26.0-26.5.1.
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 patches: Safari 26.5.2, iOS/iPadOS 26.5.2, macOS Tahoe 26.5.2, tvOS 26.6, visionOS 26.6, and watchOS 26.6. Update all affected Apple devices to the latest versions.
Safari 26.5.2, iOS 26.5.2, iPadOS 26.5.2, macOS Tahoe 26.5.2
- Update Safari to version 26.5.2 or later via the App Store (macOS)
- Update iOS to version 26.5.2 or later via Settings > General > Software Update (iPhone)
- Update iPadOS to version 26.5.2 or later via Settings > General > Software Update (iPad)
- Update macOS Tahoe to version 26.5.2 or later via System Preferences > Software Update
- After updating, restart the device/browser to ensure the 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
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43712 — 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-43712 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