CVE-2026-0110: Google Android · Elevation of Privilege
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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0110, organizations and users should: 1) Monitor official Google security advisories and apply security patches immediately once they become available, as patching the kernel vulnerability is critical. 2) Employ mobile device management (MDM) solutions to enforce timely updates and restrict installation of untrusted applications. 3) Limit network exposure of Android devices by using VPNs, firewalls, and network segmentation to reduce attack surface. 4) Disable or restrict unnecessary services and features that could be exploited remotely, particularly those related to cellular message handling. 5) Implement behavioral monitoring and endpoint detection and response (EDR) solutions capable of identifying anomalous kernel-level activities. 6) Educate users about the risks and encourage cautious use of network connections, especially on untrusted Wi-Fi. 7) For enterprises, consider deploying Android Enterprise Recommended devices that receive timely security updates. 8) Maintain regular backups of critical data to enable recovery in case of compromise. These steps go beyond generic advice by focusing on proactive patch management, network controls, and detection capabilities tailored to kernel-level threats.
Description
In MM_DATA_IND of cn_NrSmMsgHdlrFromMM.cpp, there is a possible EoP due to memory corruption. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.