Quick answers
- Is CVE-2026-64700 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64700 being exploited in the wild.
- How severe is CVE-2026-64700?
- Informational severity, with a CVSS score of 5.5, published 27 July 2026.
- Which products and versions are affected?
- Apple iPadOS < 26.6; Apple macOS < 15.7.8; Apple Tvos < 26.6; Apple Visionos < 26.6; and 1 more.
- Is there a fix for CVE-2026-64700?
- 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-64700 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-64700?
- Check whether you run Apple iPadOS, Apple macOS, Apple Tvos 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
A use-after-free vulnerability was identified in multiple Apple operating systems, including iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. The issue stems from improper memory management, which can be triggered by a local application. An attacker could exploit this to cause a denial-of-service condition (unexpected system termination). Apple has addressed the issue by improving memory management in the latest software updates. Fixes are available 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 < 26.6
- Apple macOS Sequoia < 15.7.8
- Apple macOS Sonoma < 14.8.8
- Apple macOS Tahoe < 26.6
- Apple tvOS < 26.6
- Apple visionOS < 26.6
- Apple watchOS < 26.6
Timeline
- 2026-07-27: disclosed
- 2026-07-27: patched