Skip to main content
VulnerabilityPublished Updated

CVE-2025-32318: Google Android · Elevation of Privilege

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

  1. Monitor official Google and Android security advisories closely for the release of patches addressing CVE-2025-32318 and prioritize immediate deployment on all affected Android 16 devices.
  2. Until patches are available, restrict installation and execution of untrusted or third-party applications, especially those requiring graphics rendering capabilities.
  3. Employ runtime protections such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) where supported to mitigate exploitation attempts.
  4. Implement strict privilege separation and least privilege principles to limit the potential impact of any successful exploitation.
  5. Use mobile device management (MDM) solutions to enforce security policies and monitor for anomalous behavior indicative of exploitation attempts.
  6. Educate users and administrators about the risk and encourage vigilance against suspicious activity or unexpected device behavior.
  7. Consider network-level controls to limit exposure of vulnerable devices to untrusted networks.
  8. Conduct regular security audits and penetration testing focusing on mobile device security posture to identify and remediate related weaknesses.

Description

In Skia, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…