Kernel-memory disclosure via insufficient log redaction
Published Mar 25, 2026 · Updated Mar 25, 2026
Information disclosure in the Kernel of Apple iOS, iPadOS, macOS, visionOS, and watchOS allows local users to read kernel memory. The Kernel logging path records sensitive kernel-memory contents without sufficient redaction, exposing them to an app able to read the affected log output. A locally executed app is required; Apple has not disclosed the affected log site or whether sandbox privileges constrain access.
Summary
What happened
Information disclosure in the Kernel of Apple iOS, iPadOS, macOS, visionOS, and watchOS allows local users to read kernel memory. The Kernel logging path records sensitive kernel-memory contents without sufficient redaction, exposing them to an app able to read the affected log output. A locally executed app is required; Apple has not disclosed the affected log site or whether sandbox privileges constrain access.
The record
- CVE
- CVE-2026-28868
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 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 <18.7.7
- Affected versionversion=0 <26.4
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