dbcve.org
SafariWeb browser · Apple

CVE-2026-20652

HIGH · 7.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 →
84/100
Remediation priority · High
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.3, iOS 18.7.5 and iPadOS 18.7.5, iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, visionOS 26.3. A remote attacker may be able to cause 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 Safari, iOS, iPadOS, macOS Tahoe, and visionOS allows a remote attacker to cause a denial-of-service. The issue was addressed with improved memory handling in the fixed versions.

MitigationApply the vendor-supplied updates: Safari 26.3, iOS/iPadOS 18.7.5 and 26.3, macOS Tahoe 26.3, and 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 the Apple product in use
    Determine whether the device is running Safari (browser), iOS (iPhone), iPadOS (iPad), macOS (Mac computer), or visionOS (Vision Pro headset)
    Affected if The product is one of Safari, iOS, iPadOS, macOS, or visionOS and the version falls within the affected ranges
  2. Check Safari browser version
    Open Safari, go to Safari menu > About Safari, and note the version number shown
    Affected if Safari version is lower than 26.3
  3. Check iOS version on iPhone
    Go to Settings > General > About on the iPhone and note the version number
    Affected if iOS version is lower than 18.7.5, OR is 26.0 or higher but lower than 26.3
  4. Check iPadOS version on iPad
    Go to Settings > General > About on the iPad and note the version number
    Affected if iPadOS version is lower than 18.7.5, OR is 26.0 or higher but lower than 26.3
  5. Check macOS version
    Click Apple menu > About This Mac and note the version number displayed
    Affected if macOS version is lower than 26.3
  6. Check visionOS version
    Go to Settings > General > About on the Vision Pro device and note the version number
    Affected if visionOS version is lower than 26.3

The environment is affected if any Safari, iOS, iPadOS, macOS, or visionOS installation matches the specified version ranges (below 26.3 for most, or below 18.7.5 for iOS/iPadOS in the lower range).

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 the vendor-supplied updates: Safari 26.3, iOS/iPadOS 18.7.5 and 26.3, macOS Tahoe 26.3, and visionOS 26.3.

Recommended fix High confidence

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

  1. Identify the Apple device and current OS version (Settings > General > About)
  2. For iPhone/iPad: Go to Settings > General > Software Update and update to iOS/iPadOS 18.7.5 or iOS/iPadOS 26.3
  3. For Mac: Go to System Settings > General > Software Update and update to macOS Tahoe 26.3
  4. For Safari: Update via App Store or system software update to Safari 26.3
  5. For Vision Pro: Go to Settings > General > Software Update and update to visionOS 26.3
  6. Restart the device after updating to apply the changes
Caveat Standard OS update risks apply - ensure backups before updating; some legacy apps may not be compatible with major OS version jumps

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-2026-20652 — 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-20652 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