Local privilege escalation via permission-prompt tapjacking
Published Mar 2, 2026 · Updated Mar 2, 2026
Tapjacking in Google Android 14 through 16 allows local users to gain privileges by overlaying a permission-acceptance interface. The flaw is in writeToParcel in WindowInfo.cpp; Google identifies the overlay path but has not disclosed which serialized field or validation failure permits obscured input. Exploitation requires local access but no additional execution privileges; Google states that user interaction is not needed.
Summary
What happened
Tapjacking in Google Android 14 through 16 allows local users to gain privileges by overlaying a permission-acceptance interface. The flaw is in writeToParcel in WindowInfo.cpp; Google identifies the overlay path but has not disclosed which serialized field or validation failure permits obscured input. Exploitation requires local access but no additional execution privileges; Google states that user interaction is not needed.
The record
- CVE
- CVE-2026-0007
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-1021, CAPEC-506, T1068
- 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
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