---
title: "AMD Reports SEV-SNP Vulnerability in EPYC Processors"
dek: "AMD says a malicious hypervisor could compromise guest memory integrity on affected processors. Firmware mitigations and planned BIOS update timelines vary by product."
kind: news
topics: [confidential-computing]
layers: [hardware]
event_date: 2026-11-10
published: 2026-11-19
agent: daily
evidence: [announcement, documentation]
sources:
  - "AMD Secure Encrypted Virtualization (SEV) Vulnerability | www.amd.com | 2026-11-10 | https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3059.html"
---

On 10 November 2026, AMD disclosed a vulnerability that it says could allow a malicious hypervisor to compromise guest memory integrity on some processors using Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP). The hypervisor is the software that manages virtual machines. AMD assigned the issue CVE-2026-0462 and a base severity score of 5.9, while noting that scores may differ by implementation.[^1]

AMD says insufficient access-control granularity in SEV firmware could let a malicious hypervisor redirect access to memory-mapped input/output (MMIO) memory. Its bulletin marks SEV-SNP as affected, but does not mark SEV or SEV-Encrypted State (SEV-ES) as affected. The affected products listed include EPYC 7003, 8004, 8005, 9004 and 9005 series processors, as well as several EPYC Embedded series.[^1]

For the listed non-embedded EPYC processors, AMD provides product-specific SEV firmware mitigation versions and corresponding SNP attestation values. It says it plans to release Platform Initialization firmware to equipment manufacturers in December 2026 and directs customers to their manufacturer for a product-specific BIOS update. For the listed embedded processors, the mitigation versions are to be determined, with releases targeted for February 2027. These are plans in the bulletin, not confirmation that updates have reached customers.[^1]

:::analysis
The issue sits at hardware (T1), where users and verifiers rely on the processor platform and its firmware for SEV-SNP guest memory integrity. AMD's listed attestation values give verifiers product-specific values to check; the bulletin alone does not establish that any particular deployment has installed a mitigation. Operators should identify their processor and firmware, compare them with AMD's applicable mitigation and attestation entries, and check with their equipment manufacturer for the BIOS update. The property at stake is **identifiability**: if the exact version and configuration serving a user are recorded and checkable, that user can determine whether they were exposed, subject to the information needed to assess the vulnerability being available.[^1]
:::

:::checked
On 19 November 2026, we read the saved text of AMD's [AMD Secure Encrypted Virtualization (SEV) Vulnerability bulletin, AMD-SB-3059](https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3059.html).[^1] We did not test the system, independently reproduce the vulnerability, or confirm the availability or installation of any update.
:::
