dbcve.org
SafariWeb browser · Apple

CVE-2026-20608

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.7.5 / 26.3 or later.
See remediation →
58/100
Remediation priority · Elevated
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
This issue was addressed through improved state management. This issue is fixed in Safari 26.3, iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, visionOS 26.3. 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 state management vulnerability in WebKit (Safari browser engine) allows maliciously crafted web content to trigger an unexpected process crash (denial of service). This affects Safari 26.3, iOS 18.7.5/26.3, iPadOS 18.7.5/26.3, macOS Tahoe 26.3, and visionOS 26.3.

MitigationApply vendor patches by updating Safari, iOS, iPadOS, macOS, and visionOS to the fixed versions (Safari 26.3, iOS/iPadOS 18.7.5 or 26.3, macOS Tahoe 26.3, visionOS 26.3).

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.3
IpadosOperating system
Affected:< 18.7.5>= 26.0, < 26.3
Iphone OsOperating system
Affected:< 18.7.5>= 26.0, < 26.3
macOSOperating system
Affected:< 26.3
VisionosOperating system
Affected:< 26.3

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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. Check Safari version on macOS
    Open Safari, go to Safari > About Safari, or run: system_profiler SPApplicationsDataType | grep -i safari
    Affected if Safari version is less than 26.3
  2. Check iOS version on iPhone
    Go to Settings > General > About on the device, or check via Finder/iTunes when connected to a computer
    Affected if iOS version is less than 18.7.5, or is 26.0 through 26.2
  3. Check iPadOS version on iPad
    Go to Settings > General > About on the device
    Affected if iPadOS version is less than 18.7.5, or is 26.0 through 26.2
  4. Check macOS version
    Click Apple menu > About This Mac, or run: sw_vers
    Affected if macOS version is less than 26.3 (any release name, such as Tahoe)
  5. Check visionOS version
    Go to Settings > General > About on the Vision Pro device
    Affected if visionOS version is less than 26.3
  6. Identify WebKit-using applications
    Review installed third-party browsers (Chrome, Firefox, Edge) which bundle their own engines, versus Safari which uses the system WebKit
    Affected if The affected version of Safari or any app using the vulnerable system WebKit is in use

You are affected if any device runs Safari, iOS, iPadOS, macOS, or visionOS with a version lower than the fixed releases (Safari/macOS/visionOS < 26.3, iOS/iPadOS < 18.7.5 or 26.0-26.2), and the user could potentially visit malicious web content through a WebKit-based browser.

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 18.7.5 / 26.3 or later
Fixed in 18.7.526.3
Interim mitigation

Apply vendor patches by updating Safari, iOS, iPadOS, macOS, and visionOS to the fixed versions (Safari 26.3, iOS/iPadOS 18.7.5 or 26.3, macOS Tahoe 26.3, visionOS 26.3).

Recommended fix High confidence

Upgrade to Safari 26.3, iOS 18.7.5/iPadOS 18.7.5, iOS 26.3/iPadOS 26.3, macOS Tahoe 26.3, or visionOS 26.3 depending on your device

  1. Check current device version: On iOS/iPadOS go to Settings > General > About; On macOS go to System Settings > About; On Safari check Safari > About Safari
  2. For iOS/iPadOS: Go to Settings > General > Software Update and install iOS 18.7.5 or iOS 26.3 / iPadOS 18.7.5 or iPadOS 26.3
  3. For macOS: Go to System Settings > General > Software Update and install macOS Tahoe 26.3
  4. For visionOS: Go to Settings > General > Software Update and install visionOS 26.3
  5. For Safari: Update Safari through system software update to version 26.3

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.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-2026-20608 — 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-2026-20608 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