dbcve.org
SafariWeb browser · Apple

CVE-2025-43214

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-30
Fix available
A fix is available. Upgrade to 2.6 / 11.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The 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 · moderate confidence

A memory handling vulnerability in WebKit (Safari's rendering engine) allows maliciously crafted web content to trigger an unexpected browser crash. This affects Safari 18.6, iOS 18.6, iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, and watchOS 11.6 across desktop and mobile Apple platforms.

MitigationApply vendor-supplied patches by updating affected devices to Safari 18.6, iOS/iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, or watchOS 11.6 as appropriate for each platform.

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
Affected:< 18.6
IpadosOperating system
Affected:< 18.6
Iphone OsOperating system
Affected:< 18.6
macOSOperating system
Affected:< 15.6
TvosOperating system
Affected:< 18.6
VisionosOperating system
Affected:< 2.6
WatchosOperating system
Affected:< 11.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apple platform
    Determine which Apple device and operating system you are using (iPhone, iPad, Mac, Apple TV, Apple Watch, or Apple Vision Pro)
    Affected if The device runs any of the affected Apple platforms
  2. Check Safari version on macOS
    Open Safari, go to Safari menu > About Safari to view the installed version number
    Affected if Safari version is below 18.6 (e.g., 18.5.x or earlier)
  3. Check iOS or iPadOS version
    Go to Settings > General > About on iPhone or iPad to view the iOS/iPadOS version
    Affected if iOS or iPadOS version is below 18.6
  4. Check macOS version
    Go to Apple menu > About This Mac to view the macOS version
    Affected if macOS version is below 15.6 (e.g., 15.5.x or earlier)
  5. Check tvOS, visionOS, or watchOS version
    Open Settings > General > About on Apple TV, Apple Vision Pro, or Apple Watch to view the tvOS, visionOS, or watchOS version
    Affected if tvOS is below 18.6, visionOS is below 2.6, or watchOS is below 11.6

You are affected if your Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS version is below the respective threshold (18.6 for Safari/iOS/iPadOS/tvOS, 15.6 for macOS, 2.6 for visionOS, 11.6 for watchOS) and you browse web content, since the vulnerability is triggered when WebKit processes malicious web pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.6 / 11.6 / 15.6 or later
Fixed in 2.611.615.6
Interim mitigation

Apply vendor-supplied patches by updating affected devices to Safari 18.6, iOS/iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, or watchOS 11.6 as appropriate for each platform.

Recommended fix High confidence

Safari 18.6, iOS 18.6, iPadOS 18.6, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6

  1. Check current Safari version via Safari > About Safari (macOS) or Settings > General > About (iOS/iPadOS)
  2. Check current macOS version via Apple menu > About This Mac
  3. Check current iOS/iPadOS version via Settings > General > About
  4. Check current tvOS version via Settings > General > About
  5. Check current watchOS version via Settings > General > About
  6. Check current visionOS version via Settings > General > About
  7. Update Safari to version 18.6 or later
  8. Update iOS to version 18.6 or later
Caveat Upgrading to major OS versions (iOS 18, macOS 15) may introduce user-facing changes; ensure compatibility with existing workflows before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43214 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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