Kernel-layout disclosure via uninitialized memory handling
Published Sep 14, 2026 · Updated Sep 14, 2026
Memory initialization flaws in Apple operating systems before their listed fixed releases allow local users to determine kernel memory layout. Apple identifies the issue only as faulty memory initialization and has not published the affected kernel component or operation. A locally installed app is required; the disclosed consequence is exposure of kernel layout information, with no reported direct memory-content disclosure or modification.
Summary
What happened
Memory initialization flaws in Apple operating systems before their listed fixed releases allow local users to determine kernel memory layout. Apple identifies the issue only as faulty memory initialization and has not published the affected kernel component or operation. A locally installed app is required; the disclosed consequence is exposure of kernel layout information, with no reported direct memory-content disclosure or modification.
The record
- CVE
- CVE-2026-65405
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 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.7
- Affected versionversion=0 <27
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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