Skip to main content
CVE-2025-22430VulnerabilityPublished

CVE-2025-22430: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.5Medium
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:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =15
Fixed in–

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Monitor for official patches or security updates from Google addressing CVE-2025-22430 and apply them promptly once available. 2) Enforce strict physical security controls to prevent unauthorized local access to Android 15 devices, including device lock policies, secure storage, and employee awareness training. 3) Implement mobile device management (MDM) solutions to enforce security policies, restrict local access capabilities, and monitor device integrity. 4) Limit the use of Android 15 devices in high-risk environments until patches are applied. 5) Conduct regular audits of device permissions and installed applications to detect potential privilege escalations or suspicious activities. 6) Encourage encryption of sensitive data on devices to reduce the impact of information disclosure. 7) Prepare incident response plans for potential data leakage incidents involving mobile devices. These measures go beyond generic advice by focusing on controlling local access, enforcing device security policies, and preparing for incident handling specific to this vulnerability.

Description

In isInSignificantPlace of multiple files, there is a possible way to access sensitive information 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.

References

Community reviews

Loading reviews…