dbcve.org
SafariWeb browser · Apple

CVE-2026-20644

MEDIUM · 6.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 →
72/100
Remediation priority · Elevated
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.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 memory handling vulnerability in WebKit allows processing of maliciously crafted web content to cause an unexpected process crash. The fix involved improved memory handling, suggesting the original issue may have been a memory corruption type defect such as use-after-free or similar memory management flaw.

MitigationApply vendor-supplied updates: Safari 26.3, iOS/iPadOS 18.7.5 and 26.3, macOS Tahoe 26.3, and visionOS 26.3. Until patched, limit web browsing to trusted sources and disable JavaScript in untrusted contexts if possible.

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

CVSS:3.1/AV:N/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 the installed Safari version
    Open Safari and go to Safari > About Safari (macOS) or Settings > General > About (iOS/iPadOS). Record the version number shown.
    Affected if The version is below 26.3 for Safari on any platform
  2. Check the installed iOS or iPadOS version
    Go to Settings > General > About on the device and note the version number.
    Affected if The version is below 18.7.5 or falls between 26.0 and 26.3 inclusive
  3. Check the installed macOS version
    Click the Apple menu and select About This Mac. Note the version number.
    Affected if The macOS version is below 26.3 (referenced as Tahoe 26.3 in updates)
  4. Confirm WebKit is in use
    Verify that Safari or any WebKit-based browser is used for web browsing. This vulnerability affects the WebKit rendering engine specifically.
    Affected if WebKit-based browsers process web content on the device
  5. Assess JavaScript execution context
    Determine whether JavaScript is enabled in the browser settings. This vulnerability is triggered by processing maliciously crafted web content.
    Affected if JavaScript is enabled and untrusted web pages can be loaded

A user is affected if they run an unpatched version (Safari, macOS, or visionOS below 26.3; iOS/iPadOS below 18.7.5 or between 26.0-26.3) AND use WebKit to process untrusted web content with JavaScript enabled

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-supplied updates: Safari 26.3, iOS/iPadOS 18.7.5 and 26.3, macOS Tahoe 26.3, and visionOS 26.3. Until patched, limit web browsing to trusted sources and disable JavaScript in untrusted contexts if possible.

Recommended fix High confidence

Upgrade to Safari 26.3, iOS 18.7.5, iOS 26.3, iPadOS 18.7.5, iPadOS 26.3, macOS Tahoe 26.3, or visionOS 26.3 as appropriate for your device

  1. Identify the currently installed version of Safari, iOS, iPadOS, macOS, or visionOS on the affected device
  2. For iOS/iPadOS devices: Navigate to Settings > General > Software Update and install the available update (iOS 18.7.5 or iOS 26.3/iPadOS 26.3 depending on device)
  3. For macOS devices: Open System Settings > General > Software Update and install macOS Tahoe 26.3
  4. For visionOS devices: Open Settings > General > Software Update and install visionOS 26.3
  5. For Safari standalone: Update through the App Store or system software update to Safari 26.3
  6. After updating, verify the version by checking About or the Safari version to confirm the fix is applied
Caveat Standard Apple security updates typically do not introduce breaking changes; however, major version updates (e.g., to iOS 26) may include UI or feature changes

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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