CVE-2026-20713

MEDIUMPre-NVD 4.54.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.5Exploit: None knownExposed services: Not assessed

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

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
4.5
EG Score
4.5MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100CISA SSVC

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
Severity45% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

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.20260227.1 (210 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
intel-microcode0.20080131-1 ... 3.20260227.1 (210 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 on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 136 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-20713?
CVE-2026-20713 is a medium vulnerability 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 CVE-2026-20713 disclosed?
CVE-2026-20713 was first published on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20713?
CVE-2026-20713 has a CVSS base score of 4.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-20713?
No fix for CVE-2026-20713 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. 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