dbcve.org
SafariWeb browser · Apple

CVE-2025-43419

HIGH · 8.8 CVSS v3.1 Published 2025-11-04
Fix available
A fix is available. Upgrade to 26.0 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, iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. 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 · high confidence

Memory corruption vulnerability in WebKit affecting Safari 26, iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, and watchOS 26. Processing maliciously crafted web content triggers improper memory handling, potentially allowing arbitrary code execution.

MitigationApply the vendor-supplied updates (Safari 26, iOS/iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26 or later) to all affected devices. 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.0
IpadosOperating system
Affected:< 26.0
Iphone OsOperating system
Affected:< 26.0
TvosOperating system
Affected:< 26.0
VisionosOperating system
Affected:< 26.0
WatchosOperating system
Affected:< 26.0

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. Identify the device and operating system
    Check the installed OS version: On iPhone/iPad go to Settings > General > About. On Mac go to Apple menu > About This Mac. On Apple TV go to Settings > General > About. On Apple Watch go to Settings > General > About.
    Affected if The OS version is any version prior to 26.0 (for example, iOS 25.x, macOS Sequoia 25.x, etc.)
  2. Check Safari version on macOS or iOS
    On macOS: Open Safari > Safari menu > About Safari. On iOS/iPadOS: Go to Settings > Safari > About. Note the version number displayed.
    Affected if The Safari version shown is earlier than 26.0
  3. Identify any third-party browsers using WebKit
    Review installed browsers - many third-party iOS/macOS browsers use WebKit as their rendering engine. Check the app version in the App Store or the application's About section.
    Affected if A WebKit-based browser older than version 26.0 corresponding to the OS is installed
  4. Confirm WebKit exposure through apps
    On macOS, check Applications folder for apps known to use WebKit (alternative browsers, RSS readers, email clients with HTML rendering). Note that some macOS apps embed WebKit for web content display.
    Affected if Any WebKit-using application is present on an unpatched OS version prior to 26.0

The environment is affected if any Apple device is running an OS version (or Safari version on that OS) earlier than 26.0 and processes untrusted web content through Safari or any WebKit-based application.

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.0 or later
Fixed in 26.0
Interim mitigation

Apply the vendor-supplied updates (Safari 26, iOS/iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26 or later) to all affected devices. Until patched, avoid visiting untrusted websites.

Recommended fix High confidence

Safari 26, iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26

  1. For iPhone and iPod touch: Go to Settings > General > Software Update and install iOS 26
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 26
  3. For Mac (if applicable): Go to System Settings > General > Software Update and install macOS Tahoe 26
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 26
  5. For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 26
  6. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 26
  7. For Safari browser on macOS: Update via macOS system update to get Safari 26

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
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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