Privilege escalation via insecure coprocessor memory defaults
Published Nov 10, 2026 · Updated Nov 10, 2026
Insecure defaults in Google Android allow local users to escalate privileges by modifying coprocessor memory from non-secure software. The defaults permit writes to coprocessor instruction and data memory; the retrieved record does not identify the affected functions or settings. Exploitation requires System execution privileges and no user interaction, and the published applicability is Pixel-family specific.
Summary
What happened
Insecure defaults in Google Android allow local users to escalate privileges by modifying coprocessor memory from non-secure software. The defaults permit writes to coprocessor instruction and data memory; the retrieved record does not identify the affected functions or settings. Exploitation requires System execution privileges and no user interaction, and the published applicability is Pixel-family specific.
The record
- CVE
- CVE-2026-95404
- Published
- Nov 10, 2026
- Updated
- Nov 10, 2026
- Vendor
- Product
- Android
- Classifications
- T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 10, 2026CVE publishedPublication date reported by the CVE source.
- Nov 10, 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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us