CVE-2026-20501

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.4; sources differ by 0.0.

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

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

In vdec, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11262030; Issue ID: MSV-9197.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 7, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 7, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

September 2026 MediaTek Security Bulletin

https://www.mediatek.com/product-security-bulletin/September-2026

Vendor Advisories for CVE-2026-20501(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 60× 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-20 20:43 UTCEG score recompute
  2. 2026-09-20 20:43 UTCGHSA enrichment
  3. 2026-09-20 20:15 UTCEPSS rescore
  4. 2026-09-20 09:32 UTCGHSA enrichment
  5. 2026-09-19 22:19 UTCEG score recompute
  6. 2026-09-19 22:19 UTCGHSA enrichment
  7. 2026-09-19 11:03 UTCGHSA enrichment
  8. 2026-09-18 23:51 UTCEG score recompute
  9. 2026-09-18 23:51 UTCGHSA enrichment
  10. 2026-09-18 19:27 UTCEPSS rescore
  11. 2026-09-18 12:39 UTCGHSA enrichment
  12. 2026-09-18 01:27 UTCEG score recompute
  13. 2026-09-18 01:27 UTCGHSA enrichment
  14. 2026-09-17 14:15 UTCGHSA enrichment
  15. 2026-09-17 02:59 UTCGHSA enrichment
  16. 2026-09-16 15:13 UTCEG score recompute
  17. 2026-09-16 15:13 UTCGHSA enrichment
  18. 2026-09-16 14:07 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-16 04:01 UTCGHSA enrichment
  21. 2026-09-15 16:47 UTCGHSA enrichment
  22. 2026-09-15 05:35 UTCEG score recompute
  23. 2026-09-15 05:35 UTCGHSA enrichment
  24. 2026-09-14 18:21 UTCGHSA enrichment
  25. 2026-09-14 06:15 UTCGHSA enrichment
Show 35 more
  1. 2026-09-13 19:03 UTCEG score recompute
  2. 2026-09-13 19:03 UTCGHSA enrichment
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 07:50 UTCGHSA enrichment
  5. 2026-09-12 20:39 UTCEG score recompute
  6. 2026-09-12 20:39 UTCGHSA enrichment
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-12 09:27 UTCGHSA enrichment
  9. 2026-09-11 22:14 UTCEG score recompute
  10. 2026-09-11 22:14 UTCGHSA enrichment
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-11 11:02 UTCEG score recompute
  13. 2026-09-11 11:02 UTCGHSA enrichment
  14. 2026-09-10 23:50 UTCGHSA enrichment
  15. 2026-09-10 12:35 UTCEG score recompute
  16. 2026-09-10 12:35 UTCGHSA enrichment
  17. 2026-09-10 09:34 UTCEPSS rescore
  18. 2026-09-10 01:23 UTCGHSA enrichment
  19. 2026-09-09 14:10 UTCGHSA enrichment
  20. 2026-09-09 02:58 UTCEG score recompute
  21. 2026-09-09 02:58 UTCGHSA enrichment
  22. 2026-09-08 22:00 UTCEPSS rescore
  23. 2026-09-08 19:54 UTCGHSA enrichment
  24. 2026-09-08 16:15 UTCGHSA enrichment
  25. 2026-09-08 04:19 UTCGHSA enrichment
  26. 2026-09-07 22:35 UTCEG score recompute
  27. 2026-09-07 22:35 UTCGHSA enrichment
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-07 11:23 UTCGHSA enrichment
  30. 2026-09-07 10:46 UTCEG score recompute▲ 8.40
  31. 2026-09-07 10:45 UTCGHSA enrichment
  32. 2026-09-07 10:41 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  33. 2026-09-07 02:29 UTCNVD update
  34. 2026-09-07 02:05 UTCEG score recompute
  35. 2026-09-07 02:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20501?
CVE-2026-20501 is a high vulnerability published on September 7, 2026. In vdec, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS11262030; Issue ID: MSV-9197.
When was CVE-2026-20501 disclosed?
CVE-2026-20501 was first published in the National Vulnerability Database on September 7, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20501 actively exploited?
CVE-2026-20501 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-20501?
CVE-2026-20501 has a CVSS v3.1 base score of 8.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-20501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20501, 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-20501

Explore →

Is Your Infrastructure Affected by CVE-2026-20501?

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

Start Free Scan →Browse All CVEs