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.
CVE-2026-0110
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026Pixel Update Bulletin—March 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/pixel/2026/2026-03-01Android Security Bulletin—March 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/2026/2026-03-01Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:44 UTCEG score recompute
- 2026-07-27 13:44 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-120
- CVE-2010-10016EG 10.0CRITICAL
- CVE-2012-10035EG 10.0CRITICAL
- CVE-2011-4862EG 10.0EPSS p100HIGH
- CVE-2008-3496EG 10.0HIGH
- CVE-2007-1770EG 10.0EPSS p97HIGH
- CVE-2002-1337EG 10.0EPSS p99HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-1999-1237EG 10.0EPSS p94HIGH
- CVE-1999-0385EG 10.0EPSS p97HIGH
Frequently asked(5)
What is CVE-2026-0110?
When was CVE-2026-0110 disclosed?
Is CVE-2026-0110 actively exploited?
What is the CVSS score of CVE-2026-0110?
How do I remediate CVE-2026-0110?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-0110
Is Your Infrastructure Affected by CVE-2026-0110?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.