Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-26417: Information disclosure in Google Android

0
Medium
VulnerabilityCVE-2025-26417cvecve-2025-26417
Published: Tue Aug 26 2025 (08/26/2025, 22:48:58 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Android

Description

In checkWhetherCallingAppHasAccess of DownloadProvider.java, there is a possible bypass of user consent when opening files in shared storage due to a confused deputy. 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/03/2025, 01:08:54 UTC

Technical Analysis

CVE-2025-26417 is a medium-severity information disclosure vulnerability found in the DownloadProvider component of Google Android versions 12 through 15. The flaw exists in the method checkWhetherCallingAppHasAccess within DownloadProvider.java, where a confused deputy problem allows a bypass of user consent when opening files located in shared storage. This vulnerability arises because the system incorrectly grants access to files without properly verifying the calling application's permissions, effectively allowing an unprivileged local app to access sensitive data stored in shared storage without requiring any additional execution privileges or user interaction. The vulnerability is classified under CWE-610 (Improper Restriction of XML External Entity Reference), indicating a logic flaw that leads to unintended information exposure. Exploitation requires only local access to the device, no authentication, and no user interaction, making it feasible for malicious apps or processes already present on the device to silently extract sensitive information. Although no known exploits are currently reported in the wild, the vulnerability's presence in widely used Android versions and its ability to bypass user consent mechanisms make it a notable risk for data confidentiality on affected devices. The CVSS v3.1 score is 4.0, reflecting a low attack vector (local), low complexity, no privileges required, no user interaction, and limited impact confined to confidentiality only, with no integrity or availability impact.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to mobile devices running affected Android versions, which are commonly used by employees for business communications, data access, and remote work. The information disclosure could lead to leakage of sensitive corporate or personal data stored on shared storage, including documents, credentials cached by apps, or other confidential files. This could facilitate further targeted attacks, espionage, or data breaches, especially in sectors handling sensitive information such as finance, healthcare, government, and critical infrastructure. Since exploitation requires local access, the threat is heightened if devices are lost, stolen, or if malicious apps are installed, whether intentionally or via social engineering. The lack of user interaction requirement increases the stealthiness of the attack, making detection more difficult. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach can have significant compliance and reputational consequences under European data protection regulations like GDPR.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Ensure all Android devices are updated to patched versions once Google releases fixes for CVE-2025-26417. Until patches are available, restrict installation of untrusted or third-party applications to reduce risk of local exploitation. 2) Implement Mobile Device Management (MDM) solutions to enforce application whitelisting, control app permissions, and monitor for suspicious activity related to file access. 3) Educate users on the risks of installing unknown apps and the importance of device security hygiene. 4) Encrypt sensitive data stored on shared storage to limit the impact of unauthorized access. 5) Regularly audit and monitor device logs for unusual file access patterns that could indicate exploitation attempts. 6) For highly sensitive environments, consider restricting use of shared storage or isolating critical data within secure containers or apps with stronger access controls. These measures go beyond generic advice by focusing on controlling local app behavior and data protection at the device level.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 68ae3d1cad5a09ad005c3c2b

Added to database: 8/26/2025, 11:02:52 PM

Last enriched: 9/3/2025, 1:08:54 AM

Last updated: 10/11/2025, 2:45:00 PM

Views: 60

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 are available only with a Pro account. Contact root@offseq.com for access.

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