CVE-2026-40668 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization (SEV) firmware has an authentication bypass by spoofing. A malicious hypervisor can use it to request attestation reports for VMPL 0, the most privileged level inside a confidential virtual machine.
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.
Teams running AMD SEV confidential virtual machines, where the hypervisor is the untrusted party. The sources do not name affected firmware versions or products, so unknown.
Not affected if no-amd-sev
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
No fix yet, per the sources.
Authentication bypass by spoofing in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to request attestation reports for VMPL 0.
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:L/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.