Local privilege escalation via background launch logic
Published Jun 1, 2026 · Updated Jun 1, 2026
Privilege escalation in the Framework component of Google Android 16 QPR2 allows local users to launch applications in the background. The resumeConfigurationDispatch method in ActivityRecord.java incorrectly permits a background application launch during configuration resume instead of enforcing the platform's launch restriction. A low-privileged local application can trigger the flaw without user interaction and use the prohibited launch to gain elevated privileges on the device.
Summary
What happened
Privilege escalation in the Framework component of Google Android 16 QPR2 allows local users to launch applications in the background. The resumeConfigurationDispatch method in ActivityRecord.java incorrectly permits a background application launch during configuration resume instead of enforcing the platform's launch restriction. A low-privileged local application can trigger the flaw without user interaction and use the prohibited launch to gain elevated privileges on the device.
The record
- CVE
- CVE-2026-0077
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-693
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 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-qpr2
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