AMD EPYC™ Embedded 3000 Series Processors signature verification bypass in PSP Boot ROM
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
AMD EPYC Embedded 3000 Series and EPYC 7001 Series processors fail to properly verify cryptographic signatures in the PSP Boot ROM. An attacker with local access to the SPI flash, without logging in or any user action, can bypass secure boot, run unsigned code with full Platform Security Processor privilege, and compromise the host boot chain's confidentiality and integrity, causing lasting loss of availability.
Written by a model
Original description
Improper verification of a cryptographic signature in the PSP Boot ROM of AMD Zeppelin (Zen1/Zen+) processors could allow an attacker with local access to the SPI flash to bypass secure boot authentication, potentially resulting in arbitrary unsigned code execution at full Platform Security Processor privilege, loss of confidentiality, loss of integrity of the host boot chain, and persistent loss of availability.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-74127 (Improper verification of a cryptographic signature in the PSP Boot ROM of AMD Zeppelin (Zen1/Zen+) processors could allow an attacker with…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-74127 (entry last updated 2026-11-21):
Affected:
- AMD AMD EPYC™ Embedded 3000 Series Processors: version range not reported
- AMD AMD EPYC™ 7001 Series Processors: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-74127 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-74127 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-7075.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-74127
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-74127"}.Affected versions
- AMD AMD EPYC™ Embedded 3000 Series ProcessorsVersion range not reported
- AMD AMD EPYC™ 7001 Series ProcessorsVersion range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | amd.com · en/resources/product-security/bulletin/AMD-SB-7075.html |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-74127 |
| Record | NVD · CVE-2026-74127 |
Related
- CVE-2025-52533Improper Access Control in an on-chip debug interface could allow a privileged attacker to enable a debug interface and potentially compromi
- CVE-2026-0432Incorrect default permissions in the installation directory for the AMD chipset driver could allow an attacker to achieve privilege escalati
- CVE-2025-61963Improper input validation within the AmdPlatformRasSmm driver could allow an attacker with privileged access to overwrite SMRAM…
- CVE-2025-0008Insufficient verification of data authenticity may allow a local attacker to bypass Secure Debug Unlock (SDU), potentially resulting in…
- CVE-2023-31364Improper handling of direct memory writes in the input-output memory management unit could allow a malicious guest virtual machine (VM) to f
- CVE-2024-36354Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a sys
No corrections so far. Something wrong on this page? Report an error.