CVE-2025-0033: AMD EPYC™ 7003 Series Processors (formerly codenamed "Milan") · Improper Access Control
Affects AMD EPYC™ 7003 Series Processors (formerly codenamed "Milan")Source CVE Database V5
Not known to be exploited · CVSS 6.0 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2025-0033, European organizations should implement the following specific measures: 1) Enforce strict access controls and monitoring on administrative accounts to prevent unauthorized privilege escalation or misuse. 2) Limit the number of users with high-level privileges on hosts running AMD EPYC 7003 processors and SEV-SNP enabled virtual machines. 3) Monitor system logs and audit trails for unusual activities related to SEV-SNP initialization and RMP modifications. 4) Apply firmware, microcode, or software patches provided by AMD as soon as they become available to address this vulnerability. 5) Employ hardware attestation and integrity verification tools to detect anomalies in SEV-SNP guest memory mappings. 6) Consider additional isolation measures such as network segmentation and strict tenant separation in multi-tenant environments. 7) Engage with cloud service providers to confirm their patching status and mitigation strategies if using hosted infrastructure. These steps go beyond generic advice by focusing on administrative privilege management and monitoring specific to the vulnerable component.
Description
Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.