Skip to main content
VulnerabilityPublished Updated

CVE-2026-0116: 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 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =Android kernel
Fixed in–

AI-suggested

  1. Apply official security patches from Google immediately once they become available to address the vulnerability in the Android kernel.
  2. Until patches are released, restrict network exposure of Android devices, especially limiting access to untrusted networks and disabling unnecessary services that process media data.
  3. Employ mobile device management (MDM) solutions to enforce security policies, including restricting installation of untrusted applications and controlling media input sources.
  4. Utilize kernel-level exploit mitigations such as Kernel Address Space Layout Randomization (KASLR), stack canaries, and memory protection features where supported to reduce exploitation success.
  5. Monitor security advisories and threat intelligence feeds for emerging exploit code or attack campaigns targeting this vulnerability.
  6. Educate users and administrators about the risk and encourage prompt updates and cautious handling of media files from untrusted sources.
  7. For organizations, implement network segmentation and intrusion detection systems tuned to detect anomalous behavior related to kernel exploits.
  8. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) tools capable of identifying exploitation attempts at the kernel level.

Description

In __mfc_handle_released_buf of mfc_core_isr.c, there is a possible out of bounds write due to a missing bounds check. 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…