Skip to content
Web

CVE-2026-64713

8.1
High
EPSS 0.47%Patch availableJul 29, 2026

Safari flaw lets websites detect whether a user visited specific links.

common questions

Is CVE-2026-64713 being exploited?

Not confirmed. CVE-2026-64713 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-64713?

CVE-2026-64713 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64713?

Yes. A fix has been recorded for CVE-2026-64713. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64713 affect?

CVE-2026-64713 affects Safari < 26.6, iOS < 26.6, iPadOS < 26.6, macOS Tahoe < 26.6, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64713?

Update Safari and Apple OSes to 26.6+ immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Safari < 26.6iOS < 26.6iPadOS < 26.6macOS Tahoe < 26.6tvOS < 26.6visionOS < 26.6watchOS < 26.6
impact

Remote websites can determine if a user visited particular links, enabling cross-site tracking, profiling and privacy breaches.

action required

Patch when possible

affected versions
Apple iOS and iPadOS
  • affected< 26.6
Apple macOS
  • affected< 26.6
Apple Safari
  • affected< 26.6
Apple tvOS
  • affected< 26.6
Apple visionOS
  • affected< 26.6
Apple watchOS
  • affected< 26.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free