Skip to content
NewA calmer, faster ZeroHour

Mior attack reads AMD SEV-SNP guest memory and skews attestation

Original title: Mior Attack Breaks AMD SEV-SNP Security, Enabling Arbitrary Memory Access and Forged Attestation

GBHackersby Divya ()2 min read
Part of a story covered by 5 sourcesETH Zurich’s Mior attack can rewrite AMD SEV-SNP VM memoryMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

ETH Zurich showed a hostile host with a PCIe device can rewrite confidential VM memory; AMD rates CVE-2026-0462 at 5.9.

Researchers at ETH Zurich say a malicious cloud host can read and modify confidential virtual-machine memory and obtain misleading SEV-SNP attestation reports. The Mior attack, CVE-2026-0462, abuses a mismatch between the Platform Security Processor’s Reverse Map Table and AMD Infinity Fabric routing, using a peripheral that appears as system memory. It assumes hypervisor and firmware-configuration control plus an attached PCIe device. AMD lists SEV firmware mitigations dated August 12, 2026, with later platform-initialization firmware targets.

Unconfirmed: The research demonstration is not described as exploitation by attackers outside the lab.

Key facts
  • On a Zen 5 EPYC 9135, memory reads and writes succeeded in all 1,000 trials.
  • Ciphertext hiding on or off did not change that result.
  • A modified guest still received a platform-signed report of a benign launch measurement.
  • Affected lines are EPYC 7003, 8004, 8005, 9004, 9005 and several embedded EPYC processors.
  • Server platform firmware is targeted for December 2026 and embedded platforms for February 2027.
Security assessment · AI, from the articlePublic proof of concept

Impact: arbitrary guest-memory access and misleading remote attestation

ProductAffectedFixed in
AMD EPYC server processors with SEV-SNPEPYC 7003, 8004, 8005, 9004 and 9005, plus several embedded EPYC linesSEV firmware mitigations dated August 12, 2026; server PI firmware targeted December 2026; embedded February 2027
What to do
  1. 1.Install the BIOS update for the exact server model from its manufacturer.
  2. 2.Check AMD attestation security versions and reject outdated versions before releasing secrets.
  3. 3.Ask the cloud provider which hosts have received the mitigation.
Analyze CVE-2026-0462 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-0462
———

From the original article

2 min read at gbhackers.com

Researchers have shown that a malicious cloud host can read and modify the memory of confidential virtual machines. They can also produce misleading attestation reports by exploiting a vulnerability in AMD Secure Encrypted Virtualization with Secure Nested Paging (SEV-SNP). This attack, known as Mior and tracked as CVE-2026-0462, targets the hardware protections meant to keep […]

GBHackers

By Divya · gbhackers.com

Read the full article at GBHackers

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.