CVE-2025-22413VulnerabilityPublished 26 Aug 2025

CVE-2025-22413: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.0Medium

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

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% 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 2026-10-25.

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

AI-suggested

To mitigate CVE-2025-22413 effectively, European organizations should: 1) Monitor official Google and Android security advisories closely for patches addressing this vulnerability and prioritize timely deployment once available. 2) Implement strict application control policies on Android devices, limiting installation to trusted sources and using Mobile Device Management (MDM) solutions to enforce app vetting and permissions. 3) Restrict physical access to Android devices, especially in sensitive environments, to prevent local exploitation. 4) Employ runtime protection and behavior monitoring on Android devices to detect anomalous local processes that might attempt to exploit kernel vulnerabilities. 5) Educate users about the risks of installing untrusted applications and the importance of device security hygiene. 6) Consider deploying endpoint detection and response (EDR) tools capable of monitoring Android devices for suspicious local activity. 7) For organizations developing Android-based products or custom ROMs, conduct thorough code reviews focusing on kernel logic and error handling to prevent similar logic errors. These steps go beyond generic patching advice by emphasizing proactive device management, access control, and monitoring tailored to the nature of this local information disclosure vulnerability.

Description

In multiple functions of hyp-main.c, there is a possible privilege escalation 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.

Impact

For European organizations, the impact of CVE-2025-22413 depends largely on the prevalence of Android devices within their environment and the sensitivity of the data stored or processed on those devices. Since the vulnerability allows local information disclosure without privilege escalation or user interaction, it poses a risk primarily to environments where untrusted or potentially malicious applications can be installed or where physical access to devices is possible. Enterprises with Bring Your Own Device (BYOD) policies or those that rely heavily on Android devices for sensitive operations could face risks of data leakage or reconnaissance by attackers aiming to gather kernel-level information. While the vulnerability does not directly allow code execution or system compromise, the disclosed information could be leveraged in multi-stage attacks, especially in targeted espionage or advanced persistent threat (APT) scenarios. This is particularly relevant for sectors such as government, defense, finance, and critical infrastructure within Europe, where data confidentiality is paramount. Additionally, since no user interaction is required, the vulnerability could be exploited silently by malicious apps or insiders with local access. The lack of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation once details become more widely known.

CWE-703Improper Check or Handling of Exceptional Conditions (opens in a new tab)
Pillar weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (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

Description

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

WeaknessesCWE-703

Technical details

References

Community reviews

Related threats