AMD Chip Flaw Lets GPU Bypass VM Protections

Researchers disclosed the Mior attack, which uses a graphics card to undermine AMD SEV-SNP memory protections on EPYC servers.

Updated on Nov. 18, 2026 in Cybersecurity

Bold vector editorial illustration of a single coral graphics card in a server slot, with a thin line of light linking it to a processor socket.
Researchers disclosed the Mior attack, tracked as CVE-2026-0462, which lets a graphics card undermine AMD SEV-SNP memory protections on EPYC servers. AI Illustration. Upload story photo >

Researchers disclosed the Mior attack, tracked as CVE-2026-0462, which uses a graphics card to bypass AMD SEV-SNP protections on confidential virtual machines. AMD's November 10 security bulletin lists SEV-SNP as affected, while the older SEV and SEV-ES modes are not listed.

Why it matters

The attack can give a modified virtual machine read and write access to a production-style guest and let it spoof a legitimate guest's launch measurement. Because the attack requires control of the hypervisor and system firmware along with access to a PCIe device, it targets environments where a malicious host is already a concern.

The researchers demonstrated Mior on a Zen 5 AMD EPYC 9135 server, and CVE-2026-0462 carries a CVSS 4.0 score of 5.9. The disclosure does not establish whether the flaw has been exploited outside the research setting.

The players

AMD

Advanced Micro Devices is a major American semiconductor company that designs the EPYC server processors and SEV-SNP security features affected by the vulnerability.

The details

The GPU did not crack the encryption or recover the key; instead, a malicious host interfered with setting up the Reverse Map Table, which records page ownership and access, and some setup writes from the AMD Platform Security Processor reached graphics card memory instead of system memory.

Timeline

  1. November 10, 2026: AMD publishes its security bulletin listing SEV-SNP as affected.

  2. August 12, 2026: AMD's listed SEV firmware fix date for EPYC 7003, 8004, 8005, 9004 and 9005 processors.

  3. December 2026: AMD targets related platform firmware releases to server makers.

  4. 2027: Separate target dates are set for several embedded EPYC models.

The Tech Race

The Mior disclosure is a setback for AMD's SEV-SNP line, which was built to keep cloud virtual machines isolated even from the host, and it extends a pattern of confidential-computing research that tests the trust boundary between hardware and hypervisor. The finding puts AMD in direct comparison with rival chip makers that offer their own encrypted virtual machine features.

Operators of cloud servers running AMD EPYC processors with SEV-SNP should check AMD's bulletin and confirm when firmware fixes reach their hardware. Because the attack requires a malicious hypervisor and physical PCIe access, the practical risk is highest in multi-tenant environments where the host itself is not fully trusted.

The takeaway

Hardware-based isolation for cloud virtual machines depends on the host firmware and attached devices being trustworthy, so organizations should track vendor firmware schedules closely rather than assume SEV-SNP protects against a malicious host.

What happens next

AMD has targeted December 2026 for related platform firmware releases to server makers, with separate embedded EPYC model dates set for 2027.

Further reading

For more on how threats to server hardware are tracked, explore Cybersecurity coverage on Wisevoter.