Local privilege escalation via improper input validation
Published Sep 15, 2026 · Updated Sep 15, 2026
Out-of-bounds writes in the Android kernel allow local users with System execution privileges to elevate privileges without user interaction. Multiple undisclosed kernel locations improperly validate input before writing beyond buffer boundaries; Google has not published the affected functions or input paths. Exploitation starts from a local System-privileged context and crosses a higher privilege boundary, while no specific affected kernel release is public.
Summary
What happened
Out-of-bounds writes in the Android kernel allow local users with System execution privileges to elevate privileges without user interaction. Multiple undisclosed kernel locations improperly validate input before writing beyond buffer boundaries; Google has not published the affected functions or input paths. Exploitation starts from a local System-privileged context and crosses a higher privilege boundary, while no specific affected kernel release is public.
The record
- CVE
- CVE-2026-55332
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Product
- Android
- Classifications
- T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=Android kernel
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
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