CVE-2025-0027 · Infrastructure
NO FIX YET
AMD SEV firmware has an access control flaw that lets a malicious hypervisor bypass Reverse Map Table protections. This can compromise the integrity of SEV-SNP guest memory.
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.
Systems running AMD EPYC processors with SEV-SNP confidential virtual machines, where the hypervisor is not fully trusted. Teams that do not run SEV-SNP guests are not exposed through this flaw. The sources do not name affected firmware versions.
Not affected if intel-hardware, no-sev-snp-guests
Who cares amd, confidential-computing, hypervisor, sev-snp
Unknown from the sources.
No fix yet, per the sources.
Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially impacting the integrity of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory.
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.