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-2025-0076: Information disclosure in Google Android

0
Low
VulnerabilityCVE-2025-0076cvecve-2025-0076
Published: Thu Sep 04 2025 (09/04/2025, 18:33:45 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In multiple locations, there is a possible way to view icons belonging to another user due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

AI-Powered Analysis

AILast updated: 09/11/2025, 20:20:16 UTC

Technical Analysis

CVE-2025-0076 is a low-severity information disclosure vulnerability affecting multiple versions of the Google Android operating system, specifically versions 13, 14, and 15. The vulnerability arises from a missing permission check in several locations within the Android system, which allows a local attacker to view icons belonging to other users on the same device. This flaw is categorized under CWE-862 (Missing Authorization), indicating that the system fails to properly enforce access control policies. Exploitation does not require any additional execution privileges beyond those of a local user, nor does it require any user interaction, making it potentially easier to exploit in multi-user environments. However, the impact is limited to local information disclosure, specifically the ability to view icons associated with other users, which may reveal some metadata or user-specific information but does not compromise system integrity or availability. The CVSS v3.1 base score is 3.3, reflecting low severity due to the limited confidentiality impact, the requirement for local access, and the absence of integrity or availability impacts. There are currently no known exploits in the wild, and no patches have been explicitly linked in the provided information, suggesting that remediation may be pending or integrated into future Android updates. The vulnerability highlights the importance of strict permission checks in multi-user operating systems to prevent unauthorized access to user-specific data, even if that data appears minimal such as icons or UI elements.

Potential Impact

For European organizations, the direct impact of CVE-2025-0076 is relatively limited due to its low severity and local scope. However, in environments where Android devices are shared among multiple users—such as in corporate settings with shared devices, kiosks, or public terminals—this vulnerability could lead to inadvertent leakage of user-specific information. Although the disclosed information (icons) may seem trivial, it could potentially be used as part of a larger reconnaissance effort to profile users or infer usage patterns. This could be a privacy concern under regulations like GDPR, especially if combined with other data. The vulnerability does not allow privilege escalation or remote exploitation, so the risk to critical infrastructure or sensitive systems is minimal. Nonetheless, organizations with strict data privacy requirements should consider this vulnerability as part of their overall mobile device security posture. The lack of user interaction requirement means that an attacker with local access could exploit this silently, which may be relevant in insider threat scenarios or in environments with less physical security.

Mitigation Recommendations

To mitigate CVE-2025-0076, European organizations should ensure that all Android devices are updated to the latest available security patches as soon as Google releases fixes addressing this vulnerability. Until patches are available, organizations should limit physical and local access to Android devices, especially those used in multi-user contexts. Implementing strict device usage policies and employing mobile device management (MDM) solutions can help enforce user separation and monitor for suspicious local activity. Additionally, organizations should audit multi-user configurations on Android devices to minimize unnecessary user accounts and restrict access rights appropriately. For environments where shared devices are necessary, consider deploying custom lockdown or kiosk modes that limit user switching or access to other users' data. Finally, raising user awareness about the risks of shared device usage and enforcing strong authentication mechanisms can reduce the likelihood of exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
google_android
Date Reserved
2024-12-13T16:55:53.516Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68b9dcc488499799243c2ef1

Added to database: 9/4/2025, 6:39:00 PM

Last enriched: 9/11/2025, 8:20:16 PM

Last updated: 10/16/2025, 7:32:53 PM

Views: 17

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats