CVE-2026-0003 · Infrastructure
NO FIX YET
The AMD ASP Bootloader uses a static key shared across parts, so an attacker can install older, vulnerable Secure Encrypted Virtualization firmware. Once the firmware is downgraded, known flaws can be used to decrypt guest memory.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems that run AMD EPYC processors with Secure Encrypted Virtualization for confidential virtual machines are the ones exposed. The sources do not name affected firmware versions or which platforms are covered. Teams that do not use AMD SEV or confidential computing can skip it.
Not affected if no-amd-sev, non-amd-hardware
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
No fix yet, per the sources.
Use of a per-part static key in the ASP Bootloader could allow an attacker to downgrade the Secure Encrypted Virtualization (SEV) firmware and exploit known vulnerabilities to decrypt memory potentially resulting in loss of confidentiality.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.