Local privilege escalation via unchecked channel data
Published Sep 8, 2026 · Updated Sep 8, 2026
Out-of-bounds write in Android 16, 16 QPR2, and 17 allows local users to elevate privileges through openLogicalChannel. The openLogicalChannel implementations in multiple System-component files process channel data without the required bounds check, allowing a write beyond the destination buffer. A low-privileged local user can trigger the flaw without user interaction and gain higher privileges, affecting device confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Android 16, 16 QPR2, and 17 allows local users to elevate privileges through openLogicalChannel. The openLogicalChannel implementations in multiple System-component files process channel data without the required bounds check, allowing a write beyond the destination buffer. A low-privileged local user can trigger the flaw without user interaction and gain higher privileges, affecting device confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-55285
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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=16
- Affected versionversion=16-qpr2
- Affected versionversion=17
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