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%, top 99% of all CVEs by exploit prediction. 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%CVSS: 4.5Exploit: None knownExposed: 0

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

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.5(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity45% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 31× 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-08-20 02:32 UTCEG score recompute
  2. 2026-08-20 02:32 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 04:51 UTCGHSA enrichment
  5. 2026-08-18 07:10 UTCEG score recompute
  6. 2026-08-18 07:10 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 09:27 UTCEG score recompute
  9. 2026-08-17 09:27 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 11:46 UTCEG score recompute
  12. 2026-08-16 11:46 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 14:06 UTCEG score recompute
  15. 2026-08-15 14:06 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 16:24 UTCEG score recompute
  18. 2026-08-14 16:24 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 18:43 UTCGHSA enrichment
  21. 2026-08-12 21:03 UTCGHSA enrichment
  22. 2026-08-12 16:35 UTCEG score recompute
  23. 2026-08-12 16:35 UTCGHSA enrichment
  24. 2026-08-12 16:03 UTCEG score recompute
  25. 2026-08-12 16:03 UTCGHSA enrichment
Show 6 more
  1. 2026-08-12 15:27 UTCEG score recompute
  2. 2026-08-12 15:27 UTCGHSA enrichment
  3. 2026-08-12 13:50 UTCEPSS rescore
  4. 2026-08-11 17:45 UTCEG score recompute
  5. 2026-08-11 16:46 UTCEG score recompute
  6. 2026-08-11 16:45 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-20713?
CVE-2026-20713 has a CVSS v3 base score of 4.5 (NVD).
How do I remediate CVE-2026-20713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20713, 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-20713

Explore →

Is Your Infrastructure Affected by CVE-2026-20713?

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