Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2026-64772

A critical vulnerability (CVE‑2026‑64772) allows a remote attacker to write data beyond the intended memory bounds in Apple operating systems. This can cause applications to crash or corrupt memory, potentially leading to denial‑of‑service or more severe exploits. The flaw is fixed in newer releases of iOS, iPadOS, macOS, tvOS, and visionOS.

publishedJul 27, 2026
last modifiedJul 29, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
33th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 27, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Apple devices running iOS, iPadOS, macOS, tvOS, or visionOS versions prior to the following releases: iOS 26.6, iPadOS 26.6, macOS Sequoia 15.7.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6. Users of older versions are at risk.

02

Real-world impact

An attacker who can send crafted data to a vulnerable application can cause that application to crash or corrupt memory, which may lead to denial‑of‑service or enable further exploitation of the device.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability requires no authentication, no user interaction, and provides complete compromise of confidentiality, integrity, and availability. The out‑of‑bounds write can affect any process, making it highly dangerous.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade your device to the latest OS version: iOS 26.6 or later, iPadOS 26.6 or later, macOS Sequoia 15.7.8 or later, macOS Tahoe 26.6 or later, tvOS 26.6 or later, or visionOS 26.6 or later.
  2. 02Restart the device after the update to ensure all components are refreshed.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 27, 2026 · 3d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 28, 2026 · 2d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →