dbcve.org
SafariWeb browser · Apple

CVE-2025-43433

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 26.1, iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. Processing maliciously crafted web content may lead to memory corruption.

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

Memory corruption vulnerability in WebKit (Safari's browser engine) that triggers when processing maliciously crafted web content. The issue was addressed with improved memory handling, suggesting a use-after-free or similar memory management flaw in the browser's rendering process.

MitigationUpdate all affected Apple devices to Safari 26.1, iOS/iPadOS 18.7.2 or 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, or watchOS 26.1 as appropriate. Until patched, avoid visiting untrusted websites.

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:< 26.1
IpadosOperating system
Affected:< 26.1
Iphone OsOperating system
Affected:< 26.1
TvosOperating system
Affected:< 26.1
VisionosOperating system
Affected:< 26.1
WatchosOperating system
Affected:< 26.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Check Safari version on macOS
    Open Safari, go to Safari > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal
    Affected if Version is below 26.1
  2. Check iOS/iPadOS version on iPhone/iPad
    Go to Settings > General > About, look at the 'Software Version' field
    Affected if Version is below 26.1 (or below 18.7.2 if that is also listed as fixed)
  3. Check tvOS version on Apple TV
    Go to Settings > General > About > Version, or check Settings > System > Software Updates
    Affected if Version is below 26.1
  4. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to My Watch > General > About, or check directly on Apple Watch in Settings > General > About
    Affected if Version is below 26.1
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About on the device
    Affected if Version is below 26.1
  6. Verify WebKit is in use
    Confirm the device runs Safari or any app that uses WebKit for rendering web content (this is the default state for Safari and many Apple apps)
    Affected if The device processes web content via WebKit, which is the default behavior for affected Safari versions

The device is affected if it runs any Safari/WebKit-using application with a version below 26.1 (or below 18.7.2 for iOS/iPadOS if applicable per official Apple advisories).

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 26.1 or later
Fixed in 26.1
Interim mitigation

Update all affected Apple devices to Safari 26.1, iOS/iPadOS 18.7.2 or 26.1, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, or watchOS 26.1 as appropriate. Until patched, avoid visiting untrusted websites.

Recommended fix High confidence

Upgrade to Safari 26.1, iOS/iPadOS 18.7.2 or 26.1 depending on current major version, tvOS 26.1, visionOS 26.1, or watchOS 26.1

  1. For Safari users: Update Safari to version 26.1 through Software Update or the App Store
  2. For iPhone users: Go to Settings > General > Software Update and upgrade to iOS 18.7.2 (if on iOS 18.x) or iOS 26.1 (if on iOS 26.x)
  3. For iPad users: Go to Settings > General > Software Update and upgrade to iPadOS 18.7.2 (if on iPadOS 18.x) or iPadOS 26.1 (if on iPadOS 26.x)
  4. For Apple TV users: Go to Settings > System > Software Updates and upgrade to tvOS 26.1
  5. For Apple Vision Pro users: Go to Settings > General > Software Update and upgrade to visionOS 26.1
  6. For Apple Watch users: On the iPhone, open the Watch app, go to General > Software Update and upgrade to watchOS 26.1
Caveat Standard minor version updates typically have low risk; ensure backups before updating

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
9.0 hours of engineering $1,600
Get the upgrade done

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

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