CVE-2026-0115

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

Score 2.1 from GitHub Security Advisory (severity: LOW) published 2026-03-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 2.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: None knownExposed: 0

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

In Trusted Execution Environment, there is a possible key leak due to side channel information disclosure. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

CVSS v3
2.1
EG Score
2.1(medium)
EG Risk
14(Track)
EG Risk 14/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
Severity21% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 10, 2026

Last Modified

June 17, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 15× 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-16 05:14 UTCEPSS rescore
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-11 09:36 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:11 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-28 21:40 UTCEPSS rescore
  12. 2026-08-27 14:24 UTCEPSS rescore
  13. 2026-08-25 13:48 UTCEPSS rescore
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 11:59 UTCEG score recompute
  20. 2026-08-16 11:59 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-12 23:12 UTCEG score recompute
  24. 2026-08-12 23:12 UTCGHSA enrichment
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 19 more
  1. 2026-08-10 23:59 UTCEPSS rescore
  2. 2026-08-09 07:37 UTCEG score recompute
  3. 2026-08-09 07:37 UTCGHSA enrichment
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-06 13:46 UTCEPSS rescore
  6. 2026-08-06 02:08 UTCEG score recompute
  7. 2026-08-06 02:08 UTCGHSA enrichment
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 15:09 UTCEPSS rescore
  10. 2026-08-03 10:35 UTCEPSS rescore
  11. 2026-08-02 17:48 UTCEG score recompute
  12. 2026-08-02 17:48 UTCGHSA enrichment
  13. 2026-08-02 02:26 UTCEPSS rescore
  14. 2026-08-01 04:15 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-28 15:36 UTCEPSS rescore
  17. 2026-07-27 14:13 UTCEPSS rescore
  18. 2026-07-27 13:44 UTCEG score recompute
  19. 2026-07-27 13:44 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-0115?
CVE-2026-0115 is a low vulnerability published on March 10, 2026. In Trusted Execution Environment, there is a possible key leak due to side channel information disclosure. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.
When was CVE-2026-0115 disclosed?
CVE-2026-0115 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-0115 actively exploited?
CVE-2026-0115 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 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-0115?
CVE-2026-0115 has a CVSS v3.1 base score of 2.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0115?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0115, 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-0115

Explore →

Is Your Infrastructure Affected by CVE-2026-0115?

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