SafariWeb browser · Apple
CVE-2025-43212
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 18.6, iOS 18.6 and iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6. Processing maliciously crafted web content may lead to an unexpected Safari 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 memory handling vulnerability in WebKit (Safari's rendering engine) allows remote attackers to cause an unexpected Safari crash by tricking users into visiting maliciously crafted web pages.
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
< 18.6< 18.6< 18.6< 15.6< 18.6< 2.6< 11.6CVSS 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.
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari. Note the version number displayed.Affected if Version is earlier than 18.6 on macOS versions before 15.6
-
Check iOS version on iPhoneOpen Settings app, tap General, tap About. Note the iOS version number.Affected if iOS version is earlier than 18.6 (iPhone OS refers to iOS)
-
Check iPadOS version on iPadOpen Settings app, tap General, tap About. Note the iPadOS version number.Affected if iPadOS version is earlier than 18.6
-
Check tvOS version on Apple TVGo to Settings > General > About Apple TV. Note the tvOS version number.Affected if tvOS version is earlier than 18.6
-
Check visionOS version on Apple Vision ProGo to Settings > General > About. Note the visionOS version number.Affected if visionOS version is earlier than 2.6
-
Check watchOS version on Apple WatchOpen Watch app on paired iPhone, go to My Watch > General > About. Note the watchOS version number.Affected if watchOS version is earlier than 11.6
A user is affected if they are running any Safari, iOS, iPadOS, tvOS, visionOS, or watchOS version below the thresholds AND they browse the web, as the vulnerability is triggered by visiting maliciously crafted web pages.
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 · scoped2.611.615.6
Update affected Apple devices to Safari 18.6 / iOS 18.6 / macOS Sequoia 15.6 or later to receive the memory handling fix.
Safari 18.6, iOS 18.6, iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6
- Upgrade Safari to version 18.6 or later
- Upgrade iOS (iPhone) to version 18.6 or later
- Upgrade iPadOS to version 18.6 or later
- Upgrade macOS to Sequoia 15.6 or later
- Upgrade tvOS to version 18.6 or later
- Upgrade visionOS to version 2.6 or later
- Upgrade watchOS to version 11.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43212 — 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-2025-43212 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