Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0012: Information disclosure in Google Android

0
Medium
VulnerabilityCVE-2026-0012cvecve-2026-0012
Published: Mon Mar 02 2026 (03/02/2026, 18:42:37 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

CVE-2026-0012 is an information disclosure vulnerability in Google Android versions 14, 15, and 16. It stems from a logic error in the setHideSensitive method of ExpandableNotificationRow. java, which may leak contact names locally. Exploitation requires no additional privileges or user interaction, making it accessible to local attackers or malicious apps with limited permissions. Although no known exploits are currently in the wild, the flaw can compromise user privacy by exposing sensitive contact information. This vulnerability affects widely used Android versions, potentially impacting millions of devices globally. No official patch links are provided yet, so mitigation relies on restricting local access and monitoring for suspicious activity. The severity is assessed as medium due to the limited scope (local information disclosure) and lack of remote exploitation. Organizations should prioritize updating devices once patches become available and review app permissions to minimize risk.

AI-Powered Analysis

AILast updated: 03/02/2026, 19:07:58 UTC

Technical Analysis

CVE-2026-0012 is a vulnerability identified in the Android operating system, specifically in versions 14, 15, and 16. The flaw exists in the setHideSensitive method within the ExpandableNotificationRow.java component, which handles notification display logic. Due to a logic error, this method can inadvertently expose contact names, leading to local information disclosure. The vulnerability does not require any additional execution privileges or user interaction, meaning that an attacker with local access—such as a malicious app running on the device or a user with physical access—can exploit it to retrieve sensitive contact information. This exposure could undermine user privacy and potentially facilitate further social engineering or targeted attacks. While no known exploits have been reported in the wild, the vulnerability's presence in recent Android versions, which have broad market penetration, increases its significance. The absence of a CVSS score and official patches indicates that the vulnerability is newly disclosed and may be under active investigation or remediation by Google. The flaw is primarily a privacy concern rather than a direct compromise of system integrity or availability.

Potential Impact

The primary impact of CVE-2026-0012 is the unauthorized disclosure of sensitive contact information stored on affected Android devices. This can lead to privacy violations, enabling attackers to gather personal data that could be used for identity theft, phishing, or social engineering attacks. Although the vulnerability does not allow remote exploitation or privilege escalation, the fact that no user interaction or elevated privileges are required lowers the barrier for exploitation by local malicious apps or insiders. Organizations relying on Android devices for communication and data storage may face increased risk of data leakage, especially in environments where devices are shared or less physically secure. The impact is largely on confidentiality, with limited effect on system integrity or availability. However, the exposure of contact names can have cascading effects on organizational security posture by facilitating targeted attacks.

Mitigation Recommendations

To mitigate CVE-2026-0012, organizations and users should: 1) Monitor for and restrict installation of untrusted or unnecessary local applications that could exploit this vulnerability. 2) Limit physical and local access to devices to trusted personnel only. 3) Apply principle of least privilege by reviewing and minimizing app permissions related to contacts and notifications. 4) Stay alert for official security updates from Google and prioritize patching affected Android versions (14, 15, and 16) as soon as patches are released. 5) Employ mobile device management (MDM) solutions to enforce security policies and control app installations. 6) Educate users about the risks of installing unknown apps and the importance of device security. 7) Consider encrypting sensitive contact data or using secure containers if supported by the device or enterprise environment. These steps go beyond generic advice by focusing on controlling local access and app permissions, which are critical given the vulnerability’s local exploitation vector.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
google_android
Date Reserved
2025-10-15T15:38:42.392Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a5db80d1a09e29cb1cb9b7

Added to database: 3/2/2026, 6:48:32 PM

Last enriched: 3/2/2026, 7:07:58 PM

Last updated: 3/2/2026, 11:06:29 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses