Skip to main content
CVE-2025-32317VulnerabilityPublished

CVE-2025-32317: 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.07% 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 5 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
  • =16
Fixed in–

AI-suggested

To mitigate the risks posed by CVE-2025-32317, European organizations should prioritize the following actions: 1) Promptly apply security updates and patches from Google as they become available for Android version 16. 2) Implement strict application control policies to limit the installation of untrusted or unnecessary apps that could exploit local vulnerabilities. 3) Employ mobile device management (MDM) solutions to enforce security configurations, monitor device integrity, and restrict local access to sensitive data. 4) Educate users about the risks of installing apps from unknown sources and encourage the use of official app stores. 5) Consider additional endpoint security solutions that can detect anomalous local activity indicative of exploitation attempts. 6) For high-risk environments, evaluate the feasibility of restricting local device access or using hardened Android builds with enhanced security features. These targeted measures go beyond generic advice by focusing on controlling local access vectors and ensuring timely patch management specific to this vulnerability.

Description

In App Widget, there is a possible Information Disclosure 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.

References

Community reviews

Loading reviews…