Kernel-state disclosure via insufficient input sanitization
Published Jun 29, 2026 · Updated Jun 29, 2026
Improper input validation in the Apple kernel on affected iOS, iPadOS, and macOS releases allows local users to read sensitive kernel state. The kernel insufficiently sanitizes input supplied by an application, allowing sensitive internal state to cross the kernel boundary. A local low-privilege account that can run an app is required; the reported consequence is limited to confidentiality, with no kernel write or service interruption.
Summary
What happened
Improper input validation in the Apple kernel on affected iOS, iPadOS, and macOS releases allows local users to read sensitive kernel state. The kernel insufficiently sanitizes input supplied by an application, allowing sensitive internal state to cross the kernel boundary. A local low-privilege account that can run an app is required; the reported consequence is limited to confidentiality, with no kernel write or service interruption.
The record
- CVE
- CVE-2026-43722
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-20, T1005
- 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.
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