Quick answers
- Is CVE-2026-64725 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64725 being exploited in the wild.
- How severe is CVE-2026-64725?
- Informational severity, with a CVSS score of 5.5, published 27 July 2026.
- Which products and versions are affected?
- Apple iPadOS Before 26.6; Apple macOS Before 26.6; Apple macOS Sonoma Before 14.8.8; Apple Tvos Before 26.6; and 2 more.
- Is there a fix for CVE-2026-64725?
- A patch was published on 2026-07-27. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64725 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-64725?
- Check whether you run Apple iPadOS, Apple macOS, Apple macOS Sonoma or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds write vulnerability exists in the memory management components of multiple Apple operating systems. The flaw is caused by insufficient bounds checking when processing data, which can be triggered by a local application. An attacker could exploit this to cause a denial-of-service (DoS) by crashing the affected system or service. Apple has addressed this issue by implementing improved bounds checking in iOS 26.6, iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, and watchOS 26.6.
Affected products
- Apple iOS and iPadOS Before 26.6
- Apple macOS Tahoe Before 26.6
- Apple macOS Sequoia Before 15.7.8
- Apple macOS Sonoma Before 14.8.8
- Apple tvOS Before 26.6
- Apple visionOS Before 26.6
- Apple: watchOS Before 26.6
Timeline
- 2026-07-27: disclosed
- 2026-07-27: advisory
- 2026-07-27: patched