Kernel memory corruption via improper memory handling
Published Aug 17, 2026 · Updated Aug 18, 2026
Memory corruption in the Kernel in Apple macOS before 26.6.2 allows local users to crash the system or corrupt kernel memory via a crafted app. Apple identifies the flaw only as a Kernel memory-handling issue and has not disclosed a file, function, or input path beyond the app-triggerable bug class. Exploitation requires code execution in an app context on the device and is bounded in the reviewed records to unexpected system termination or kernel-memory corruption.
Summary
What happened
Memory corruption in the Kernel in Apple macOS before 26.6.2 allows local users to crash the system or corrupt kernel memory via a crafted app. Apple identifies the flaw only as a Kernel memory-handling issue and has not disclosed a file, function, or input path beyond the app-triggerable bug class. Exploitation requires code execution in an app context on the device and is bounded in the reviewed records to unexpected system termination or kernel-memory corruption.
The record
- CVE
- CVE-2026-65330
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Apple
- Product
- macOS
- Classifications
- CWE-119, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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.2
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.
Weakness, pattern, technique
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