Skip to main content
VulnerabilityPublished Updated

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

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =15
  • =14
  • =13
Fixed in–

AI-suggested

To mitigate CVE-2025-26416, organizations and users should: 1) Monitor official Google Android security bulletins and apply patches immediately once released for affected versions 13, 14, and 15. 2) Employ application whitelisting and sandboxing to limit the impact of potential exploitation by restricting untrusted applications from processing unverified bitmap data. 3) Use mobile threat defense solutions that can detect anomalous behavior indicative of exploitation attempts. 4) Enforce strict network segmentation and limit exposure of Android devices to untrusted networks to reduce the attack vector. 5) Educate users about the risks of installing applications from untrusted sources, as malicious apps could exploit this vulnerability. 6) Implement runtime protections such as Control Flow Integrity (CFI) and Address Space Layout Randomization (ASLR) where possible to hinder exploitation. 7) Conduct regular security assessments and penetration testing focused on mobile platforms to identify potential exploitation paths. These measures go beyond generic patching advice by emphasizing layered defenses and proactive detection.

Description

In initializeSwizzler of SkBmpStandardCodec.cpp, 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…