dbcve.org
SafariWeb browser · Apple

CVE-2025-43211

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

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, iPadOS 17.7.9, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, watchOS 11.6. Processing web content may lead to a denial-of-service.

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 allows processing of malicious web content to trigger a denial-of-service condition. The issue is fixed in Safari 18.6, iOS/iPadOS 18.6, iPadOS 17.7.9, macOS Sequoia 15.6, tvOS 18.6, visionOS 2.6, and watchOS 11.6.

MitigationApply the vendor-provided updates for all affected Apple products to address the memory handling flaw in WebKit.

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:< 17.7.9>= 18.0, < 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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 product
    Determine which Apple device and operating system you are using: Safari browser on Mac, iPhone/iPad, Mac computer, Apple TV, Apple Watch, or Apple Vision Pro. This determines which version range applies.
    Affected if Any unpatched Apple device running the affected software listed in the CVE
  2. Check Safari version on Mac
    Open Safari, click Safari menu > About Safari. Note the version number displayed (e.g., 18.5).
    Affected if Safari version is less than 18.6
  3. Check iOS or iPadOS version on iPhone/iPad
    Go to Settings > General > About. Note the iOS version number (e.g., 18.5).
    Affected if iOS/iPadOS version is less than 18.6, or falls between 17.7.0 and 17.7.8 (inclusive)
  4. Check macOS version on Mac
    Click Apple menu > About This Mac. Note the macOS version (e.g., 15.5 Sequoia).
    Affected if macOS version is less than 15.6
  5. Check tvOS, visionOS, or watchOS version
    On Apple TV: go to Settings > General > About > Version. On Apple Watch: go to Settings > General > About. On Vision Pro: go to Settings > General > About. Note the respective OS version.
    Affected if tvOS is less than 18.6, visionOS is less than 2.6, or watchOS is less than 11.6

You are affected if your device runs any Apple operating system version listed above the corresponding fixed version for your product.

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 the vendor-provided updates for all affected Apple products to address the memory handling flaw in WebKit.

Recommended fix High confidence

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

  1. Open Settings on iPhone/iPad, go to General > Software Update, and update to iOS 18.6 or iPadOS 18.6 (or iPadOS 17.7.9 for older devices)
  2. On Mac, open System Settings > General > Software Update and update to macOS Sequoia 15.6
  3. On Apple Watch, open the Watch app on iPhone, go to General > Software Update, and update to watchOS 11.6
  4. On Apple TV, go to Settings > System > Software Updates and update to tvOS 18.6
  5. On Apple Vision Pro, go to Settings > General > Software Update and update to visionOS 2.6
  6. Open Safari on any platform and ensure it is updated as part of the OS update (Safari 18.6)

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43211 — 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-43211 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