Local contact-name disclosure via privacy-state logic
Published Mar 2, 2026 · Updated Mar 2, 2026
Information disclosure in Google Android 14 through 16 allows local users to expose a contact name from a sensitive notification. The setHideSensitive method in ExpandableNotificationRow uses an overbroad animation-skip condition when changing notification privacy state, producing an incorrect content alpha that exposes the name. Exploitation requires local access but no execution privileges or user interaction, and the reported disclosure is limited to the contact name.
Summary
What happened
Information disclosure in Google Android 14 through 16 allows local users to expose a contact name from a sensitive notification. The setHideSensitive method in ExpandableNotificationRow uses an overbroad animation-skip condition when changing notification privacy state, producing an incorrect content alpha that exposes the name. Exploitation requires local access but no execution privileges or user interaction, and the reported disclosure is limited to the contact name.
The record
- CVE
- CVE-2026-0012
- Published
- Mar 2, 2026
- Updated
- Mar 2, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-693, CWE-284, T1517
- 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