Skip to main content
VulnerabilityPublished Updated

CVE-2026-0006: Google Android · Remote Code Execution

Affects Google AndroidSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =16
Fixed in–

AI-suggested

Until official patches are released, organizations should implement several specific mitigations to reduce risk. First, restrict network exposure of Android devices running version 16 by enforcing strict firewall and network segmentation policies to limit attack surface. Employ mobile device management (MDM) solutions to monitor device behavior and enforce security policies, including disabling unnecessary services and restricting app installations from untrusted sources. Enable runtime protections such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) if configurable. Monitor network traffic and device logs for anomalous activity indicative of exploitation attempts, including unexpected remote connections or process anomalies. Educate users about the importance of timely updates and avoiding suspicious links or files, even though user interaction is not required for this exploit. Prepare for rapid deployment of official patches once available by maintaining an up-to-date asset inventory and patch management process. Consider deploying endpoint detection and response (EDR) tools capable of detecting exploitation attempts targeting heap buffer overflows. Collaborate with vendors and security communities to stay informed about emerging exploit techniques and mitigation strategies.

Description

In multiple locations, there is a possible out of bounds read and write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…