dbcve.org
SafariWeb browser · Apple

CVE-2026-64757

HIGH · 8.8 CVSS v3.1 Published 2026-07-27
Fix available
A fix is available. Upgrade to 26.6 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 3 weeks old

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
A memory corruption issue was addressed with improved state management. This issue is fixed in Safari 26.6, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6 and iPadOS 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6. Processing maliciously crafted web content may lead to an unexpected Safari 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 corruption vulnerability in WebKit (Safari) was addressed through improved state management. Processing maliciously crafted web content triggers the memory corruption, leading to unexpected Safari crashes. The CVSS 8.8 indicates potential for more severe impact beyond denial of service.

MitigationApply vendor patches: Safari 26.6, iOS/iPadOS 18.7.10 or 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6 to all affected devices. Restrict access to 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.6
IpadosOperating system
Affected:< 26.6
Iphone OsOperating system
Affected:< 26.6
macOSOperating system
Affected:>= 26.0, < 26.6
VisionosOperating system
Affected:< 26.6
WatchosOperating system
Affected:< 26.6

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 Safari version on macOS or iOS
    Open Safari and go to Safari > About Safari (macOS) or Settings > Safari > About (iOS/iPadOS). Note the version number displayed.
    Affected if The version shown is less than 26.6 (for example, 26.5.x or earlier)
  2. Identify the iOS or iPadOS version
    Open Settings > General > About on the device. Note the version number next to 'Software Version'.
    Affected if The version number is less than 26.6 (for example, 26.5.x or earlier)
  3. Identify the macOS version
    Open System Settings > General > About (or Apple menu > About This Mac). Note the version number (such as 26.0, 26.5).
    Affected if The macOS version is 26.0, 26.1, 26.2, 26.3, 26.4, or 26.5 (any version >= 26.0 but < 26.6)
  4. Identify the visionOS version
    Open Settings > General > About on the Vision Pro device. Note the version number.
    Affected if The version is less than 26.6 (for example, 26.5.x or earlier)
  5. Identify the watchOS version
    Open Settings > General > About on the Apple Watch, or open the Watch app on iPhone and go to My Watch > General > About. Note the version number.
    Affected if The version is less than 26.6 (for example, 26.5.x or earlier)

You are affected if any Apple device (Safari, iOS, iPadOS, macOS 26.0-26.5, visionOS, or watchOS) in your environment is running a version lower than 26.6, since the vulnerability exists in WebKit and can be triggered by processing malicious 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 26.6 or later
Fixed in 26.6
Interim mitigation

Apply vendor patches: Safari 26.6, iOS/iPadOS 18.7.10 or 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6 to all affected devices. Restrict access to untrusted websites until patches are applied.

Recommended fix High confidence

Safari 26.6, iOS 26.6, iPadOS 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6

  1. For iPhone/iPad: Open Settings > General > Software Update and install iOS/iPadOS 26.6
  2. For Mac: Open System Settings > General > Software Update and install macOS Tahoe 26.6
  3. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and install watchOS 26.6
  4. For Apple Vision: Go to Settings > General > Software Update and install visionOS 26.6
  5. For Safari: Update to Safari 26.6 through macOS software update or the Safari menu > About Safari

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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