CVE-2026-20901

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-08-11. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-56788 (ENISA EUVD) · GHSA-j38j-4xcw-8784 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper input validation for some Intel(R) Xeon(R) processors within firmware may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable data alteration. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (none) impacts.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 11, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
Patch available.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260925.1 (211 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260925.1 (211 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 versions)
  • every version up to 3.20260925.1: fixed in 3.20260925.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 183 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-11-11 16:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-11-10 16:43 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-11-07 19:42 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub severity MODERATE · GitHub CVSS 5.3
  8. 2026-11-07 19:42 UTCEchelonGraph re-scored
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-11-06 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-11-05 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  12. 2026-11-04 16:35 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-11-03 16:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-11-02 16:44 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-31 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-30 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-29 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-28 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-27 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-10-26 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-10-25 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-10-25 14:43 UTCEchelonGraph re-scored
  23. 2026-10-23 05:47 UTCEchelonGraph re-scored
  24. 2026-10-23 05:47 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 75 more
  1. 2026-10-20 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-18 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-10-18 03:56 UTCEchelonGraph re-scored
  4. 2026-10-16 16:41 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-14 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  6. 2026-10-13 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-10-12 16:23 UTCEchelonGraph re-scored
  9. 2026-10-11 20:05 UTCEchelonGraph re-scored
  10. 2026-10-11 17:18 UTCEchelonGraph re-scored
  11. 2026-10-11 14:50 UTCEchelonGraph re-scored
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-06 18:25 UTCEchelonGraph re-scored
  17. 2026-10-06 18:25 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-05 20:33 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  20. 2026-10-04 22:36 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  21. 2026-10-03 20:31 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  22. 2026-10-02 08:29 UTCEchelonGraph re-scored
  23. 2026-10-02 08:29 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  24. 2026-10-01 19:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-09-30 22:04 UTCEchelonGraph re-scored
  26. 2026-09-30 22:04 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  27. 2026-09-30 15:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  28. 2026-09-29 15:21 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-09-29 05:46 UTCEchelonGraph re-scored
  30. 2026-09-29 05:46 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  31. 2026-09-28 07:55 UTCEchelonGraph re-scored
  32. 2026-09-28 07:55 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  33. 2026-09-27 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  34. 2026-09-27 10:02 UTCEchelonGraph re-scored
  35. 2026-09-27 10:02 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  36. 2026-09-26 15:58 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  37. 2026-09-25 03:46 UTCEchelonGraph re-scored
  38. 2026-09-25 03:46 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  39. 2026-09-24 14:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-09-23 20:57 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  41. 2026-09-22 21:10 UTCEchelonGraph re-scored
  42. 2026-09-22 21:10 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  43. 2026-09-21 20:47 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  44. 2026-09-20 19:01 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  45. 2026-09-19 20:46 UTCEchelonGraph re-scored
  46. 2026-09-19 20:46 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  47. 2026-09-18 22:28 UTCEchelonGraph re-scored
  48. 2026-09-18 22:28 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  49. 2026-09-18 19:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-09-18 00:36 UTCEchelonGraph re-scored
  51. 2026-09-18 00:36 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  52. 2026-09-17 00:27 UTCEchelonGraph re-scored
  53. 2026-09-17 00:27 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  54. 2026-09-16 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-09-16 05:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  56. 2026-09-15 22:14 UTCEchelonGraph re-scored
  57. 2026-09-15 22:14 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  58. 2026-09-14 22:37 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  59. 2026-09-13 19:41 UTCEchelonGraph re-scored
  60. 2026-09-13 19:41 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  61. 2026-09-13 16:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-09-12 21:49 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  63. 2026-09-11 23:57 UTCEchelonGraph re-scored
  64. 2026-09-11 23:57 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  65. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  66. 2026-09-11 01:19 UTCEchelonGraph re-scored
  67. 2026-09-11 01:19 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  68. 2026-09-10 09:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  69. 2026-09-10 03:27 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  70. 2026-09-09 05:35 UTCEchelonGraph re-scored
  71. 2026-09-09 05:35 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  72. 2026-09-08 22:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-09-07 18:44 UTCEchelonGraph re-scored
  74. 2026-09-07 18:44 UTCGHSA enrichmentGHSA-j38j-4xcw-8784 · GitHub CVSS 5.3
  75. 2026-09-07 16:01 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2026-20901?
CVE-2026-20901 is a medium-severity vulnerability; its CVE record was published on August 11, 2026. Improper input validation for some Intel(R) Xeon(R) processors within firmware may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable data alteration. This result may potentially occur via local access when…
When was the CVE record for CVE-2026-20901 published?
The CVE record for CVE-2026-20901 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-20901 actively exploited?
CVE-2026-20901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20901?
CVE-2026-20901 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-20901?
A fix for CVE-2026-20901 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-20901 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-20901

Explore →

Is Your Infrastructure Affected by CVE-2026-20901?

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