CVE-2025-52537 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization firmware has an access control flaw. An attacker with administrative privileges can tamper with memory, which breaks the integrity of guest virtual machines.
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.
Hosts running AMD EPYC processors with SEV-enabled virtual machines are the systems that matter. The sources do not name affected firmware versions or say how to confirm exposure. Teams not using AMD SEV confidential virtual machines can skip it.
Not affected if no-sev-guests
Who cares amd, confidential-computing, sev, virtualization
Unknown from the sources.
No fix yet, per the sources.
Improper access control within the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to tamper with memory, potentially resulting in loss of guest memory integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/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.