CVE-2026-0116

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

March 10, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

Pixel Update Bulletin—March 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/pixel/2026/2026-03-01
generic

Android Security Bulletin—March 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-03-01

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 20× 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.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:21 UTCEPSS rescore
  16. 2026-08-28 21:40 UTCEPSS rescore
  17. 2026-08-27 14:24 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:48 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:59 UTCEG score recompute
Show 65 more
  1. 2026-08-16 11:59 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:48 UTCGHSA enrichment
  5. 2026-08-14 20:38 UTCGHSA enrichment
  6. 2026-08-14 16:17 UTCGHSA enrichment
  7. 2026-08-14 12:07 UTCGHSA enrichment
  8. 2026-08-14 07:57 UTCEG score recompute
  9. 2026-08-14 07:57 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 03:21 UTCGHSA enrichment
  12. 2026-08-12 23:11 UTCEG score recompute
  13. 2026-08-12 23:11 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-12 02:06 UTCGHSA enrichment
  16. 2026-08-11 21:56 UTCEG score recompute
  17. 2026-08-11 21:56 UTCGHSA enrichment
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 09:13 UTCGHSA enrichment
  20. 2026-08-11 05:03 UTCEG score recompute
  21. 2026-08-11 05:03 UTCGHSA enrichment
  22. 2026-08-10 23:59 UTCEPSS rescore
  23. 2026-08-10 12:56 UTCGHSA enrichment
  24. 2026-08-10 06:48 UTCGHSA enrichment
  25. 2026-08-10 02:06 UTCGHSA enrichment
  26. 2026-08-09 21:50 UTCGHSA enrichment
  27. 2026-08-09 17:40 UTCEG score recompute
  28. 2026-08-09 17:39 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 13:29 UTCGHSA enrichment
  31. 2026-08-09 07:37 UTCEG score recompute
  32. 2026-08-09 07:37 UTCGHSA enrichment
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 11:46 UTCGHSA enrichment
  35. 2026-08-08 07:28 UTCGHSA enrichment
  36. 2026-08-08 03:18 UTCGHSA enrichment
  37. 2026-08-07 23:08 UTCGHSA enrichment
  38. 2026-08-07 18:58 UTCEG score recompute
  39. 2026-08-07 18:58 UTCGHSA enrichment
  40. 2026-08-06 19:58 UTCEG score recompute
  41. 2026-08-06 19:58 UTCGHSA enrichment
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 10:31 UTCGHSA enrichment
  44. 2026-08-06 06:18 UTCGHSA enrichment
  45. 2026-08-06 02:08 UTCEG score recompute
  46. 2026-08-06 02:08 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:09 UTCEPSS rescore
  49. 2026-08-04 10:38 UTCEPSS rescore
  50. 2026-08-04 05:44 UTCGHSA enrichment
  51. 2026-08-04 01:27 UTCEG score recompute
  52. 2026-08-04 01:27 UTCGHSA enrichment
  53. 2026-08-03 10:35 UTCEPSS rescore
  54. 2026-08-03 02:27 UTCGHSA enrichment
  55. 2026-08-02 21:58 UTCGHSA enrichment
  56. 2026-08-02 17:48 UTCEG score recompute
  57. 2026-08-02 17:48 UTCGHSA enrichment
  58. 2026-08-02 02:26 UTCEPSS rescore
  59. 2026-08-01 04:15 UTCEPSS rescore
  60. 2026-07-30 16:27 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-28 15:36 UTCEPSS rescore
  63. 2026-07-27 14:13 UTCEPSS rescore
  64. 2026-07-27 13:44 UTCEG score recompute
  65. 2026-07-27 13:44 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0116?
CVE-2026-0116 is a critical vulnerability published on March 10, 2026. In mfchandlereleasedbuf of mfccore_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.
When was CVE-2026-0116 disclosed?
CVE-2026-0116 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0116 actively exploited?
CVE-2026-0116 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.5% of all scored CVEs.
What is the CVSS score of CVE-2026-0116?
CVE-2026-0116 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0116?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0116, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0116

Explore →

Is Your Infrastructure Affected by CVE-2026-0116?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs