CVE-2026-0114: Google Android · Remote Code Execution
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 30 Oct 2026, 11:52 UTC
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:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 24 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0114, organizations and users should: 1) Monitor official Google and Android security advisories closely for patches and apply them immediately once available. 2) Employ network-level protections such as firewalls and intrusion detection/prevention systems to monitor and block suspicious modem-related traffic. 3) Limit exposure of vulnerable devices by restricting unnecessary cellular network access or using VPNs to secure communications. 4) Implement device management policies that enforce timely updates and restrict installation of untrusted applications. 5) Conduct regular security audits and vulnerability assessments on Android devices within the organization. 6) Educate users about the risks and encourage cautious behavior regarding device connectivity. 7) Collaborate with mobile carriers to identify and mitigate potential exploitation attempts at the network level. Since no patches are currently available, these proactive steps are critical to reduce the attack surface and delay or prevent exploitation.
Description
In Modem, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.