CVE-2026-28248 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization firmware fails to enforce a required workflow, so a malicious hypervisor can launch a guest whose attestation report carries an ID key digest that does not match the guest's measurement. The result is loss of integrity for the guest.
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.
Affects hosts running AMD SEV confidential computing guests where the hypervisor could be malicious or compromised. The sources do not name affected firmware versions or products, so the exposed set is unknown. Teams not running AMD SEV guests on AMD hardware can likely skip it.
Not affected if no-amd-sev, non-confidential-guests
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
Unknown from the sources.
Improper enforcement of behavioral workflow in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially launch a guest whose attestation report contains an ID key digest for an ID block that doesn't match the guest's measurement resulting in loss of integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/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.