CVE-2026-28247 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization firmware has an access control flaw in mirrored or aliased memory regions. A malicious hypervisor can change the encryption bit on guest context pages, which can lead to loss of guest data integrity.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects hosts running AMD EPYC processors with SEV-enabled virtual machines under a hypervisor that could be malicious. Exposure depends on the platform firmware version, which the sources do not name. Hosts without SEV-enabled guests, and teams using managed cloud VMs where the provider handles firmware, can likely skip it, but the sources do not confirm this.
Not affected if no-sev-guests
Who cares amd, hypervisor, sev, virtualization
Unknown from the sources.
No fix yet, per the sources.
Improper Access Control Applied to Mirrored or Aliased Memory Regions in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to change the encryption bit for guest context pages potentially resulting in loss of integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.