Local privilege escalation via merged URI grants
Published Sep 8, 2026 · Updated Sep 10, 2026
Permissions bypass in Google Android 16, 16-qpr2, and 17 allows local users to gain privileges through unauthorized URI access. ActivityStarter and ActivityStartController mishandle URI-grant calculations when NeededUriGrants objects are merged, allowing required permission boundaries to be bypassed. A locally executing app can reach the affected Framework paths without user interaction and access URIs outside its assigned permissions.
Summary
What happened
Permissions bypass in Google Android 16, 16-qpr2, and 17 allows local users to gain privileges through unauthorized URI access. ActivityStarter and ActivityStartController mishandle URI-grant calculations when NeededUriGrants objects are merged, allowing required permission boundaries to be bypassed. A locally executing app can reach the affected Framework paths without user interaction and access URIs outside its assigned permissions.
The record
- CVE
- CVE-2026-28620
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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=16
- Affected versionversion=16-qpr2
- Affected versionversion=17
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