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

0
Medium
VulnerabilityCVE-2025-26442cvecve-2025-26442
Published: Thu Sep 04 2025 (09/04/2025, 17:11:59 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In onCreate of NotificationAccessConfirmationActivity.java, there is a possible incorrect verification of proper intent filters in NLS due to a logic error in the code. 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:13:49 UTC

Technical Analysis

CVE-2025-26442 is a medium-severity information disclosure vulnerability affecting Google Android versions 13, 14, and 15. The issue arises from a logic error in the NotificationAccessConfirmationActivity.java file, specifically within the onCreate method. This error leads to incorrect verification of intent filters in the Notification Listener Service (NLS), which is responsible for managing notification access permissions. Due to this flawed verification, an attacker with local access and limited privileges (PR:L) can exploit the vulnerability without requiring user interaction (UI:N) or elevated execution privileges. The vulnerability allows unauthorized disclosure of sensitive information stored or processed by the affected Android system components. The CVSS 3.1 base score is 5.5 (medium), reflecting a high impact on confidentiality (C:H) but no impact on integrity or availability. Exploitation requires local access, which limits remote exploitation but still poses a risk if an attacker gains physical or local access to the device or can execute code locally. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability is categorized under CWE-863, indicating improper authorization checks. This flaw could be leveraged by malicious applications or local attackers to extract sensitive data from the device without alerting the user or requiring their consent.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to mobile device security and data confidentiality. Many enterprises rely on Android devices for communication, access to corporate resources, and handling sensitive information. An attacker exploiting this flaw could gain unauthorized access to confidential notifications or other sensitive data on employee devices, potentially leading to data leakage or espionage. This is particularly concerning for sectors handling personal data under GDPR regulations, as unauthorized disclosure could result in compliance violations and financial penalties. The lack of required user interaction increases the risk of stealthy exploitation, making detection and prevention more challenging. Although the vulnerability requires local access, scenarios such as lost or stolen devices, insider threats, or malware with local execution capabilities could facilitate exploitation. The impact on integrity and availability is negligible, but the confidentiality breach alone is significant enough to warrant attention in environments with sensitive or regulated data.

Mitigation Recommendations

To mitigate CVE-2025-26442, European organizations should: 1) Ensure all Android devices are updated promptly once Google releases official patches for the affected versions (13, 14, 15). 2) Enforce strict device access controls, including strong authentication mechanisms (PIN, biometrics) to prevent unauthorized local access. 3) Implement Mobile Device Management (MDM) solutions to monitor device compliance, restrict installation of untrusted applications, and remotely wipe lost or stolen devices. 4) Educate users about the risks of physical device compromise and encourage secure handling of devices. 5) Limit the use of Notification Listener Service permissions to only trusted applications, as misuse of these permissions could facilitate exploitation. 6) Monitor for unusual local activity or privilege escalations that could indicate attempts to exploit local vulnerabilities. 7) Consider additional endpoint protection tools that can detect anomalous behavior related to notification access or intent filter misuse. These steps go beyond generic advice by focusing on controlling local access vectors, managing permissions tightly, and preparing for rapid patch deployment.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
google_android
Date Reserved
2025-02-10T18:29:33.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68b9d3bf88499799243bc1af

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

Last enriched: 9/11/2025, 8:13:49 PM

Last updated: 10/19/2025, 9:14:13 PM

Views: 30

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