dbcve.org
SafariWeb browser · Apple

CVE-2026-64778

MEDIUM · 6.5 CVSS v3.1 Published 2026-08-17
Fix available
A fix is available. Upgrade to 18.7.10 / 26.6.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Brand new

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 checks. This issue is fixed in Safari 26.6.1, iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6.1 and iPadOS 26.6.1, macOS Tahoe 26.6.2. Visiting a maliciously crafted website may leak sensitive data.

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
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.1
IpadosOperating system
Affected:< 18.7.10>= 26.0, < 26.6.1
Iphone OsOperating system
Affected:< 18.7.10>= 26.0, < 26.6.1
macOSOperating system
Affected:>= 26.0, < 26.6.2

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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.10 / 26.6.1 / 26.6.2 or later
Fixed in 18.7.1026.6.126.6.2
Recommended fix Moderate confidence

Safari 26.6.1, iOS 18.7.10, iPadOS 18.7.10, macOS Tahoe 26.6.2

  1. 1. Identify your current Safari, iOS, iPadOS, or macOS version from Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS), or Safari > About Safari
  2. 2. For macOS Safari users: Update to Safari 26.6.1 or later
  3. 3. For iOS users: Update to iOS 18.7.10 or later (or iOS 26.6.1 if your device supports the 26.x line)
  4. 4. For iPadOS users: Update to iPadOS 18.7.10 or later (or iPadOS 26.6.1 if your device supports the 26.x line)
  5. 5. For macOS users running macOS 26.x (Tahoe): Update to macOS Tahoe 26.6.2 or later
  6. 6. Perform the update via System Settings > General > Software Update (macOS) or Settings > General > Software Update (iOS/iPadOS)
Caveat Standard Apple update risks - ensure backup before updating; some older devices may not support these specific versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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