Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2023-20576 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

4 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2023-20576 using CVSS 7.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highpublic exploit

CVE-2023-20576

CVE-2023-20576 — Insufficient Verification of Data Authenticity in AGESA™ may allow an attacker to update SPI ROM data potentially resulting in denial of…

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.

Published Sep 2, 2026Updated Sep 2, 2026Sources: NVD, AMD (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

ahead of 0% of scored CVEs

Affects

AMD

13 products listed

CVSS base

7.7

high

Remediation

The vendor's own words where we have them.

Upgrade AMD Ryzen™ 3000 Series Desktop Processors to a fixed release (ComboAM4v2 1.2.0.B). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2023-20576

fixed0affected0not affected59

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
AMD	AMD Ryzen™ 3000 Series Desktop Processors	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ 5000 Series Desktop Processors	ComboAM4v2v 1.2.0.B	Patched
AMD	AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ 7000 Series Processors	ComboAM5 1.0.0.7b	Patched
AMD	AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ Threadripper™ PRO 5000WX Processors	ChagallWSPI-sWRX8 1.0.0.7	Patched
AMD	AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics	MendocinoPI-FT6 1.0.0.6	Patched
AMD	AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics	RembrandtPI-FP7 1.0.0.9b	Patched
AMD	AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics	RembrandtPI-FP7 1.0.0.9b	Patched
AMD	AMD Ryzen™ 7040 Series Processors with Radeon™ Graphics	PhoenixPI-FP8-FP7 1.0.0.2	Patched
AMD	AMD Ryzen™ 7045 Series Mobile Processors	DragonRangeFL1PI 1.0.0.3a	Patched
AMD	AMD Ryzen™ Embedded 5000	EmbAM4PI 1.0.0.4	Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.7	CVSS 3.1	high	2.5	5.2	amd.com (CNA), AMD (CNA), GHSA, Red Hat (VEX)

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-345 · Insufficient Verification of Data Authenticity

Varies by Context
Unexpected State::

Weakness & attack patterns

CWE-345

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-387 · Navigation Remapping To Propagate Malicious ContentCAPEC-218 · Spoofing of UDDI/ebXML MessagesCAPEC-148 · Content SpoofingCAPEC-142 · DNS Cache PoisoningCAPEC-388 · Application API Button HijackingCAPEC-386 · Application API Navigation RemappingCAPEC-384 · Application API Message Manipulation via Man-in-the-MiddleCAPEC-141 · Cache PoisoningCAPEC-111 · JSON Hijacking (aka JavaScript Hijacking)CAPEC-385 · Transaction or Event Tampering via Application API Manipulation

T1557.002Adversary-in-the-Middle: ARP Cache Poisoning
T1584.002Compromise Infrastructure: DNS Server
T1491Defacement

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.7 (AV:L)
Sep 2, 2026 · NVD
Initial · CVE published
Sep 2, 2026 · NVD
Added · GHSA-r5qj-42x4-3599 published (high)
Sep 2, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 2, 2026 · SOCRadar CTI
2023
CVE code is reserved.
Jan 1, 2023 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

3×TweetsFeb 14, 2024 – Feb 16, 2024 · SOCRadar CTI

References

6 on the record

www.amd.com/en/resources/product-security/bulletin/amd-sb-7009.html
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2023-20576
NVD
github.com/advisories/GHSA-r5qj-42x4-3599
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2023-20576
Vendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=2263271
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2023-20576
Vendor Advisory

Elsewhere on this site

AMDevery CVE for this vendor
Unclassifiedsame class
CWE-345other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2023-20576 is Insufficient Verification of Data Authenticity in AGESA™ may allow an attacker to update SPI ROM data potentially resulting in denial of…, a high vulnerability affecting AMD Ryzen™ 3000 Series Desktop Processors, AMD Ryzen™ 5000 Series Desktop Processors, AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics, AMD Ryzen™ 7000 Series Processors, AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics, AMD Ryzen™ Threadripper™ PRO 5000WX Processors, AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics, AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7040 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7045 Series Mobile Processors, AMD Ryzen™ Embedded 5000, AMD Ryzen™ Embedded V3000 from AMD. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 4 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.