Local privilege escalation via shared-UID setting reuse
Published Mar 2, 2026 · Updated Mar 2, 2026
Privilege escalation in Google Android 14, 15, 16, and 16-qpr2 allows local users to prevent location access without interaction. The Framework's enableSystemPackageLPw method attempts to reuse a disabled shared-UID package setting after update removal, but app-ID registration fails and changes the package UID. Exploitation requires local code execution but no prior privileges or user interaction, and it can leave location access unavailable.
Summary
What happened
Privilege escalation in Google Android 14, 15, 16, and 16-qpr2 allows local users to prevent location access without interaction. The Framework's enableSystemPackageLPw method attempts to reuse a disabled shared-UID package setting after update removal, but app-ID registration fails and changes the package UID. Exploitation requires local code execution but no prior privileges or user interaction, and it can leave location access unavailable.
The record
- CVE
- CVE-2026-0011
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-703, CWE-693
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2026CVE publishedPublication date reported by the CVE source.
- Mar 2, 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=14
- Affected versionversion=15
- Affected versionversion=16
- Affected versionversion=16-qpr2
What conditions does exploitation require?
What is affected?
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