CVE-2026-28248: AMD Secure Encrypted Virtualization SEV firmware integrity weakness

CVE-2026-28248 · Severity: info · Published 2026-11-10

AMD's Secure Encrypted Virtualization (SEV) firmware has an improper workflow enforcement issue that could allow a malicious hypervisor to create misleading attestation reports for encrypted virtual machines. An attacker could potentially forge proof of the VM's integrity, undermining the security guarantees that SEV is designed to provide for sensitive workloads running on shared cloud infrastructure.

Technologies: Amd Secure Encrypted Virtualization (SEV) firmware. Vendors: Amd.

Quick answers

Is CVE-2026-28248 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-28248 being exploited in the wild.
How severe is CVE-2026-28248?
Informational severity, published 10 November 2026.
Which products and versions are affected?
AMD Secure Encrypted Virtualization (SEV) firmware.
Is there a fix for CVE-2026-28248?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-28248 attacked?
It is attacked from the adjacent network, in device firmware.
Am I affected by CVE-2026-28248?
Check whether you run Amd Secure Encrypted Virtualization (SEV) firmware. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from insufficient validation of the behavioral workflow in AMD SEV firmware, allowing a malicious hypervisor to launch guests with attestation reports containing an ID key digest that does not match the guest's actual measurement. This breaks the integrity assurance of the attestation mechanism, as the report's ID block would not correspond to the guest's true state. The issue requires hypervisor-level access and affects the attestation integrity guarantee of SEV.

Affected products

  • AMD Secure Encrypted Virtualization (SEV) firmware

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.