dbcve.org
SafariWeb browser · Apple

CVE-2025-43343

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2.50.1 / 26.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 26, iOS 26 and iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, watchOS 26. Processing maliciously crafted web content may lead to an unexpected process 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 allows processing of maliciously crafted web content to cause an unexpected process crash. The high CVSS score (9.8) suggests this memory corruption may be exploitable for code execution beyond simple denial of service. This affects Safari and web rendering components across multiple Apple platforms.

MitigationUpdate to Safari 26, iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26. As a defense-in-depth measure, disable JavaScript in Safari settings or avoid untrusted websites until patches are applied.

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
macOSOperating system
Affected:< 26.0
TvosOperating system
Affected:< 26.0
VisionosOperating system
Affected:< 26.0
WatchosOperating system
Affected:< 26.0
WebkitgtkWeb browser
Affected:< 2.50.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Apple platform or WebKitGTK in use
    Determine which product is running: Safari browser, iOS, iPadOS, macOS, tvOS, visionOS, watchOS, or a WebKitGTK-based application
    Affected if Any of these products are present in the environment
  2. Check Safari version
    On macOS, go to Safari > About Safari to view the version number
    Affected if Safari version is earlier than 26.0 (e.g., 25.x or earlier)
  3. Check iOS, iPadOS, tvOS, visionOS, or watchOS version
    On the device, go to Settings > General > About to view the version
    Affected if The operating system version is earlier than 26.0 (e.g., 25.x or earlier)
  4. Check macOS version
    On Mac, go to Apple menu > About This Mac to view the macOS version
    Affected if macOS version is earlier than 26.0 (e.g., 25.x or earlier, not macOS Tahoe 26)
  5. Check WebKitGTK version
    For WebKitGTK-based applications on Linux, check the WebKitGTK package version using the system package manager (e.g., dpkg -l webkit2gtk or rpm -qi webkit2gtk)
    Affected if WebKitGTK version is earlier than 2.50.1 (e.g., 2.48.x or earlier)

The environment is affected if any Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS, or WebKitGTK installation has a version number lower than 26.0 (or 2.50.1 for WebKitGTK) and processes web content.

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

Update to Safari 26, iOS 26, iPadOS 26, macOS Tahoe 26, tvOS 26, visionOS 26, or watchOS 26. As a defense-in-depth measure, disable JavaScript in Safari settings or avoid untrusted websites until patches are applied.

Recommended fix High confidence

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

  1. For iOS devices: Update to iOS 26.0 or later via Settings > General > Software Update
  2. For iPadOS devices: Update to iPadOS 26.0 or later via Settings > General > Software Update
  3. For macOS devices: Update to macOS Tahoe 26.0 or later via System Settings > General > Software Update
  4. For Apple TV devices: Update to tvOS 26.0 or later via Settings > System > Software Updates
  5. For Apple Watch devices: Update to watchOS 26.0 or later via the Watch app on iPhone
  6. For Apple Vision Pro devices: Update to visionOS 26.0 or later via Settings > General > Software Update
  7. For Safari: Update to Safari 26.0 or later (included with macOS Tahoe 26 update)
  8. For WebKitGTK-based browsers: Update to WebKitGTK 2.50.1 or later
Caveat Standard OS update risks apply - ensure backups before updating; some older apps may become incompatible with major version updates

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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