Kernel memory write via use-after-free
Published Jul 27, 2026 · Updated Jul 27, 2026
Kernel use-after-free in Apple operating systems before 26.6 allows local users to crash the device or write kernel memory via an app. Apple identifies the Kernel component and use-after-free memory management, but does not disclose the freed object or code path that reuses it. A locally installed app must reach the vulnerable kernel path; exploitation can crash the device or modify kernel memory, with no reported data-read impact.
Summary
What happened
Kernel use-after-free in Apple operating systems before 26.6 allows local users to crash the device or write kernel memory via an app. Apple identifies the Kernel component and use-after-free memory management, but does not disclose the freed object or code path that reuses it. A locally installed app must reach the vulnerable kernel path; exploitation can crash the device or modify kernel memory, with no reported data-read impact.
The record
- CVE
- CVE-2026-64751
- Published
- Jul 27, 2026
- Updated
- Jul 27, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 27, 2026CVE publishedPublication date reported by the CVE source.
- Jul 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo