Skip to main content
VulnerabilityPublished

CVE-2025-32316: 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, 09:15 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =16
Fixed in–

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Monitor for official patches or security updates from Google and Android device manufacturers and deploy them promptly once available. 2) Restrict local access to Android devices, especially those running version 16, by enforcing strong physical security controls and device management policies. 3) Implement Mobile Device Management (MDM) solutions to control app installations and prevent execution of untrusted or malicious applications that could exploit this vulnerability locally. 4) Educate users about the risks of installing apps from untrusted sources and the importance of device security hygiene. 5) For high-risk environments, consider restricting the use of Android 16 devices until patches are available or upgrading to newer, unaffected Android versions. 6) Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of detecting anomalous local memory access patterns that might indicate exploitation attempts. These targeted controls go beyond generic advice by focusing on local access prevention, patch management, and runtime detection tailored to this specific vulnerability.

Description

In gralloc4, there is a possible out of bounds write due to a missing bounds 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…