VulnerabilityPublished 26 Aug 2025

CVE-2025-26417: Google Android · Information Disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Google Android	Affected =15 =14 =13 =12	Fixed in–

AI-suggested

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.

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.

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.

CWE-610Externally Controlled Reference to a Resource in Another Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
Attack patterns
XML Routing Detour Attacks (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Sep 2025, 01:08 UTC

WeaknessesCWE-610

Technical details

References

Community reviews

Related threats