CVE-2026-0113: 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-0113, organizations should: 1) Monitor official Google and Android security advisories closely for the release of patches or security updates addressing this kernel vulnerability and apply them immediately upon availability. 2) Employ kernel integrity monitoring tools to detect anomalous behavior or memory corruption indicative of exploitation attempts. 3) Restrict network exposure of Android devices, especially those with elevated privileges or administrative roles, by enforcing strict network segmentation and firewall rules. 4) Utilize mobile device management (MDM) solutions to enforce security policies, control app installations, and ensure timely updates. 5) Conduct regular security audits and penetration testing focusing on kernel-level vulnerabilities and privilege escalation paths. 6) Educate users and administrators about the risks of untrusted applications and the importance of applying updates promptly. 7) Consider deploying runtime exploit mitigation technologies such as Kernel Address Space Layout Randomization (KASLR) and Control Flow Integrity (CFI) where supported to reduce exploitation success. 8) Prepare incident response plans specifically addressing kernel-level compromises to enable rapid containment and recovery.
Description
In ns_GetUserData of ns_SmscbUtilities.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.