CVE-2023-20576

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. a secondary CVSS source baseline 7.7; sources differ by 0.0.

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

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

Insufficient Verification of Data Authenticity in AGESA™ may allow an attacker to update SPI ROM data potentially resulting in denial of service or privilege escalation.

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

Published

September 2, 2026

Last Modified

September 4, 2026

Vendor Advisories for CVE-2023-20576(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 29× in last 7d / 75× 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-19 15:38 UTCEPSS rescore
  2. 2026-09-19 10:08 UTCGHSA enrichment
  3. 2026-09-18 22:53 UTCEG score recompute
  4. 2026-09-18 22:53 UTCGHSA enrichment
  5. 2026-09-18 19:25 UTCEPSS rescore
  6. 2026-09-18 11:38 UTCGHSA enrichment
  7. 2026-09-18 00:17 UTCEG score recompute
  8. 2026-09-18 00:17 UTCGHSA enrichment
  9. 2026-09-17 19:24 UTCEPSS rescore
  10. 2026-09-17 13:01 UTCGHSA enrichment
  11. 2026-09-17 01:14 UTCEG score recompute
  12. 2026-09-17 01:14 UTCGHSA enrichment
  13. 2026-09-16 14:05 UTCEPSS rescore
  14. 2026-09-16 13:59 UTCEG score recompute
  15. 2026-09-16 13:59 UTCGHSA enrichment
  16. 2026-09-16 05:11 UTCEPSS rescore
  17. 2026-09-16 02:30 UTCGHSA enrichment
  18. 2026-09-15 15:15 UTCGHSA enrichment
  19. 2026-09-15 04:00 UTCEG score recompute
  20. 2026-09-15 04:00 UTCGHSA enrichment
  21. 2026-09-15 03:07 UTCEPSS rescore
  22. 2026-09-14 16:42 UTCGHSA enrichment
  23. 2026-09-14 05:27 UTCGHSA enrichment
  24. 2026-09-13 18:12 UTCEG score recompute
  25. 2026-09-13 18:12 UTCGHSA enrichment
Show 50 more
  1. 2026-09-13 16:44 UTCEPSS rescore
  2. 2026-09-13 06:57 UTCGHSA enrichment
  3. 2026-09-12 19:42 UTCEG score recompute
  4. 2026-09-12 19:42 UTCGHSA enrichment
  5. 2026-09-12 14:58 UTCEPSS rescore
  6. 2026-09-12 08:27 UTCGHSA enrichment
  7. 2026-09-11 21:11 UTCEG score recompute
  8. 2026-09-11 21:11 UTCGHSA enrichment
  9. 2026-09-11 09:56 UTCEG score recompute
  10. 2026-09-11 09:56 UTCGHSA enrichment
  11. 2026-09-11 09:34 UTCEPSS rescore
  12. 2026-09-10 22:41 UTCGHSA enrichment
  13. 2026-09-10 11:25 UTCEG score recompute
  14. 2026-09-10 11:25 UTCGHSA enrichment
  15. 2026-09-09 23:30 UTCGHSA enrichment
  16. 2026-09-09 10:31 UTCGHSA enrichment
  17. 2026-09-08 23:11 UTCEG score recompute
  18. 2026-09-08 23:11 UTCGHSA enrichment
  19. 2026-09-08 21:57 UTCEPSS rescore
  20. 2026-09-08 03:14 UTCGHSA enrichment
  21. 2026-09-07 15:59 UTCEG score recompute
  22. 2026-09-07 15:59 UTCGHSA enrichment
  23. 2026-09-07 15:59 UTCEPSS rescore
  24. 2026-09-07 04:43 UTCGHSA enrichment
  25. 2026-09-06 17:29 UTCEG score recompute
  26. 2026-09-06 17:29 UTCGHSA enrichment
  27. 2026-09-06 13:45 UTCEPSS rescore
  28. 2026-09-06 06:14 UTCGHSA enrichment
  29. 2026-09-05 18:58 UTCEG score recompute
  30. 2026-09-05 18:58 UTCGHSA enrichment
  31. 2026-09-05 15:25 UTCEPSS rescore
  32. 2026-09-05 07:43 UTCGHSA enrichment
  33. 2026-09-04 20:27 UTCEG score recompute
  34. 2026-09-04 20:27 UTCGHSA enrichment
  35. 2026-09-04 20:05 UTCEG score recompute
  36. 2026-09-04 20:05 UTCGHSA enrichment
  37. 2026-09-04 15:27 UTCEG score recompute
  38. 2026-09-04 15:27 UTCGHSA enrichment
  39. 2026-09-04 13:58 UTCEPSS rescore
  40. 2026-09-04 13:57 UTCEPSS rescore
  41. 2026-09-04 05:04 UTCEPSS rescore
  42. 2026-09-04 04:12 UTCGHSA enrichment
  43. 2026-09-03 16:54 UTCGHSA enrichment
  44. 2026-09-03 13:05 UTCEG score recompute
  45. 2026-09-03 13:05 UTCGHSA enrichment
  46. 2026-09-03 04:56 UTCEG score recompute
  47. 2026-09-03 04:55 UTCGHSA enrichment
  48. 2026-09-02 20:22 UTCEG score recompute
  49. 2026-09-02 19:51 UTCEG score recompute
  50. 2026-09-02 19:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2023-20576?
CVE-2023-20576 is a high vulnerability published on September 2, 2026. Insufficient Verification of Data Authenticity in AGESA™ may allow an attacker to update SPI ROM data potentially resulting in denial of service or privilege escalation.
When was CVE-2023-20576 disclosed?
CVE-2023-20576 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-20576 actively exploited?
CVE-2023-20576 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.5% of all scored CVEs.
What is the CVSS score of CVE-2023-20576?
CVE-2023-20576 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2023-20576?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-20576, 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-2023-20576

Explore →

Is Your Infrastructure Affected by CVE-2023-20576?

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