CVE-2026-0462: Mior
Mior is a boot-time MMIO redirection vulnerability affecting AMD Secure Encrypted Virtualization–Secure Nested Paging (SEV-SNP). An attacker controlling the host hypervisor, BIOS/UEFI, and a PCIe device can redirect AMD Platform Security Processor writes intended to initialize the Reverse Map Table (RMP) into device memory. The device supplies verification responses that allow initialization to complete while critical RMP entries, including its self-protection entry, remain uninitialized. The hypervisor can subsequently alter memory protections, enable debugging for guests that prohibit it, and invoke PSP debug operations against confidential-VM memory. AMD lists EPYC 7003, 8004, 8005, 9004, and 9005 series as affected. Researchers demonstrated the attack on a Zen 5 EPYC 9135 processor; Zen 3 and Zen 4 were not tested by the Mior team. Earlier SEV and SEV-ES modes are not identified as affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation defeats SEV-SNP guest-memory confidentiality and integrity, permitting arbitrary reads and writes of confidential-VM memory by a malicious host. Attackers can also transplant a benign VM's software measurement into a malicious VM, causing signed attestation reports to describe the benign image rather than the actual guest. This undermines remote-attestation trust and can compromise secrets released on the basis of those measurements. The demonstrated memory-access and attestation attacks also worked with ciphertext hiding enabled.
Mitigation
If you can’t patch tonight, do this now.
No vendor-supported workaround is identified. As defense in depth, enforce UEFI Secure Boot and hardware-rooted BIOS integrity protections to impede the unauthorized firmware changes required for boot-time routing manipulation. Update remote-attestation verifier policies to require AMD's fixed trusted-computing-base levels, including appropriate reported_tcb thresholds, and reject unpatched hosts before releasing decryption keys. These controls supplement rather than replace host firmware remediation.
Remediation
Patch, then assume compromise.
Install OEM-supplied host BIOS/platform firmware incorporating AMD's Mior SEV/PSP firmware fixes. AMD lists SEV firmware 1.3A.03 with MilanPI-SP3_1.0.0.L for EPYC 7003; 1.3A.4 with GenoaPI_1.0.0.K for EPYC 8004/9004; and 1.3A.0A with TurinPI_1.0.0.C for EPYC 8005/9005. The associated Mior platform releases are targeted for December 2026, with availability dependent on the server manufacturer. Follow OEM requirements for additional platform components, including BMC updates where specified. Guest-only updates do not remediate the vulnerability. Confidential-VM customers must coordinate host remediation with their infrastructure providers.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-0462 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-0462 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-0462?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-0462.
- Is there a patch for CVE-2026-0462?
- Install OEM-supplied host BIOS/platform firmware incorporating AMD's Mior SEV/PSP firmware fixes. AMD lists SEV firmware 1.3A.03 with MilanPI-SP3_1.0.0.L for EPYC 7003; 1.3A.4 with GenoaPI_1.0.0.K for EPYC 8004/9004; and 1.3A.0A with TurinPI_1.0.0.C for EPYC 8005/9005.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.