CVE-2026-20713

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2026-56474 (ENISA EUVD) · GHSA-2c6m-4rmx-m2m7 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Always-incorrect control flow implementation in some firmware for some Intel(R) Xeon(R) processors may allow an escalation of privilege. System software adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not 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 (high), integrity (high) and availability (none) impacts.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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-10). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

November 2, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
Patch available.
Web page

INTEL-SA-01442

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01442.html

Vendor Advisories for CVE-2026-20713(2)

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

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
intel-ucode—
  • every version up to 20260812-r0: fixed in 20260812-r0
—
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 6× in last 7d / 27× 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 185 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 85 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% · 1st percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-11-10 16:46 UTCEchelonGraph re-scored
  4. 2026-11-10 16:46 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7 · GitHub severity MODERATE · GitHub CVSS 7.5
  5. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-11-03 20:17 UTCEchelonGraph re-scored
  12. 2026-11-03 20:17 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7 · GitHub severity MODERATE · GitHub CVSS 7.5
  13. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  15. 2026-11-02 15:06 UTCEchelonGraph re-scored▲ 3.00
  16. 2026-11-02 15:06 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7 · GitHub severity MODERATE
  17. 2026-11-02 15:06 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  18. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  21. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  23. 2026-10-25 14:43 UTCEchelonGraph re-scored
  24. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  25. 2026-10-23 05:48 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-23 05:48 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  2. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  3. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  4. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  5. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  6. 2026-10-18 03:56 UTCEchelonGraph re-scored
  7. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  10. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-12 16:23 UTCEchelonGraph re-scored
  13. 2026-10-11 20:05 UTCEchelonGraph re-scored
  14. 2026-10-11 17:18 UTCEchelonGraph re-scored
  15. 2026-10-11 14:50 UTCEchelonGraph re-scored
  16. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  17. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  21. 2026-10-06 18:17 UTCEchelonGraph re-scored
  22. 2026-10-06 18:16 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  23. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  24. 2026-10-05 20:34 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  25. 2026-10-04 22:45 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  26. 2026-10-03 20:59 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  27. 2026-10-02 08:42 UTCEchelonGraph re-scored
  28. 2026-10-02 08:42 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  29. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  30. 2026-09-30 22:17 UTCEchelonGraph re-scored
  31. 2026-09-30 22:17 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  32. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  33. 2026-09-29 05:36 UTCEchelonGraph re-scored
  34. 2026-09-29 05:36 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  35. 2026-09-28 07:55 UTCEchelonGraph re-scored
  36. 2026-09-28 07:55 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  37. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  38. 2026-09-27 10:13 UTCEchelonGraph re-scored
  39. 2026-09-27 10:13 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  40. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  41. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  42. 2026-09-25 03:54 UTCEchelonGraph re-scored
  43. 2026-09-25 03:54 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  44. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  45. 2026-09-23 21:03 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  46. 2026-09-22 21:31 UTCEchelonGraph re-scored
  47. 2026-09-22 21:31 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  48. 2026-09-21 23:51 UTCEchelonGraph re-scored
  49. 2026-09-21 23:51 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  50. 2026-09-21 01:52 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  51. 2026-09-20 03:24 UTCEchelonGraph re-scored
  52. 2026-09-20 03:24 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  53. 2026-09-19 05:43 UTCEchelonGraph re-scored
  54. 2026-09-19 05:42 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  55. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-09-18 07:47 UTCEchelonGraph re-scored
  57. 2026-09-18 07:47 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  58. 2026-09-17 10:06 UTCEchelonGraph re-scored
  59. 2026-09-17 10:06 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  60. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-09-16 12:25 UTCEchelonGraph re-scored
  62. 2026-09-16 12:25 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  63. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-09-15 14:44 UTCEchelonGraph re-scored
  65. 2026-09-15 14:44 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  66. 2026-09-14 17:03 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  67. 2026-09-13 19:20 UTCEchelonGraph re-scored
  68. 2026-09-13 19:20 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  69. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-09-12 21:39 UTCEchelonGraph re-scored
  71. 2026-09-12 21:39 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  72. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  73. 2026-09-11 23:58 UTCEchelonGraph re-scored
  74. 2026-09-11 23:58 UTCGHSA enrichmentGHSA-2c6m-4rmx-m2m7
  75. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-20713?
CVE-2026-20713 is a high-severity vulnerability; its CVE record was published on August 11, 2026. Always-incorrect control flow implementation in some firmware for some Intel(R) Xeon(R) processors may allow an escalation of privilege. System software adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via…
When was the CVE record for CVE-2026-20713 published?
The CVE record for CVE-2026-20713 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 November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-20713 actively exploited?
CVE-2026-20713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20713?
CVE-2026-20713 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-20713?
A fix for CVE-2026-20713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-20713 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-20713

Explore →

Is Your Infrastructure Affected by CVE-2026-20713?

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

Book a Demo →Browse All CVEs