Kernel memory write via unsanitized app input
Published Jun 29, 2026 · Updated Jun 29, 2026
Improper input validation in iOS, iPadOS, and macOS before 26.5.2 allows local users to crash the system or write kernel memory. Apple identifies the Kernel component and says it inadequately sanitizes app-supplied input, but has not disclosed the affected interface or operation. Exploitation requires a locally running app; successful input can terminate the operating system or alter privileged kernel memory.
Summary
What happened
Improper input validation in iOS, iPadOS, and macOS before 26.5.2 allows local users to crash the system or write kernel memory. Apple identifies the Kernel component and says it inadequately sanitizes app-supplied input, but has not disclosed the affected interface or operation. Exploitation requires a locally running app; successful input can terminate the operating system or alter privileged kernel memory.
The record
- CVE
- CVE-2026-43724
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20, T1499.004, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 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.5.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