CVE-2026-74127 in EPYC Embedded 3000 Processors
Summary
by MITRE • 11/21/2026
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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified as improper verification of a cryptographic signature within the PSP Boot ROM of AMD Zeppelin processors represents a critical failure in the hardware-based trust anchor mechanism designed to secure system initialization. This flaw specifically affects platforms utilizing Zen1 or Zen+ architecture, where the Platform Security Processor serves as the root of trust for the entire computing environment. The core technical issue lies in the boot firmware's inability to correctly validate the digital signatures embedded within the bootloader components stored on the Serial Peripheral Interface flash memory. In a properly functioning secure boot chain, each stage of execution must cryptographically verify the integrity and authenticity of the subsequent stage before allowing it to run. However, due to this implementation error, the PSP Boot ROM fails to enforce strict signature verification protocols during specific phases of the initialization process. This deficiency creates a gap in the security boundary that separates trusted system code from untrusted or malicious inputs, effectively nullifying one of the primary defenses against low-level persistent attacks.
From an operational perspective, the impact of this vulnerability is severe and multifaceted. An attacker who has achieved local physical access to the SPI flash chip can exploit this flaw to inject unsigned or tampered firmware images into the boot process. Because the verification step is bypassed, the compromised code executes with full Platform Security Processor privileges, which are typically reserved for highly privileged system management tasks. This elevation of privilege allows the attacker to gain complete control over the host's boot chain, leading to a total loss of integrity as malicious actors can alter critical system components without detection. Furthermore, the ability to execute arbitrary unsigned code at this level compromises confidentiality by enabling the exfiltration of sensitive data protected by hardware-level encryption keys stored within the PSP. The persistence of such an attack vector also results in a persistent loss of availability, as the attacker can modify boot parameters or firmware updates to render the system unbootable or unstable over time, creating a rootkit-like presence that survives operating system reinstalls and standard software patches.
This vulnerability aligns with CWE-347, which describes Improper Verification of Cryptographic Signature, indicating a fundamental failure in ensuring that data has not been tampered with during transmission or storage. In the context of attack frameworks such as MITRE ATT&CK, this flaw facilitates techniques associated with Bootkit and Firmware persistence, specifically under tactics like Defense Evasion and Persistence. By compromising the earliest stage of system initialization, an adversary can establish a foothold that is extremely difficult to detect using conventional endpoint security solutions, which typically operate at higher privilege levels within the operating system kernel or user space. The exploitation of this flaw undermines the foundational assumptions of hardware-rooted trust models like UEFI Secure Boot and AMD's own PSP-based security features, rendering them ineffective against physically accessible targets.
Mitigation strategies for this vulnerability primarily rely on vendor-provided microcode updates and BIOS/UEFI firmware revisions that correct the signature verification logic within the PSP Boot ROM. System administrators must ensure that all affected Zeppelin-based platforms are updated to the latest stable firmware versions released by AMD or their respective OEMs, as these patches typically include hardened boot code that enforces strict cryptographic checks before executing any subsequent stages of the bootloader. Additionally, physical security controls remain essential since the attack vector requires local access to the SPI flash chip; implementing chassis intrusion detection and restricting physical access to server rooms can significantly reduce the risk of exploitation. For environments with high-security requirements, enabling additional hardware-based protections such as TPM attestation or configuring UEFI settings to prevent booting from external devices can provide layered defense mechanisms that complement the firmware fixes. Regular auditing of system integrity using tools capable of verifying low-level firmware signatures against known good baselines is also recommended to detect any unauthorized modifications before they lead to full compromise.