CVE-2026-0480 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization (SEV) firmware does not authenticate a critical function, so a malicious hypervisor can forge SEV-TIO guest request messages. This could compromise the memory integrity and confidentiality of SEV-SNP guests.
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 AMD EPYC hosts running SEV-SNP confidential guests with SEV-TIO enabled, where the hypervisor is the attacker. Operators of cloud or on-premise confidential computing platforms should look at this; teams without SEV-SNP guests can skip it. The sources do not give the affected firmware versions.
Not affected if no-sev-snp-guests, no-sev-tio
Who cares amd, confidential-computing, hypervisor, linux-kvm, sev-snp
Unknown from the sources.
No fix yet, per the sources.
Missing Authentication for Critical Function in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to forge SEV-TIO guest request messages potentially compromising SEV-SNP guest memory integrity and confidentiality.
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:H/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.