CVE-2025-48514: AMD EPYC™ 9004 Series Processors · Insufficient Granularity of Access Control
Affects AMD EPYC™ 9004 Series ProcessorsSource CVE Database V5
Not known to be exploited · CVSS 4.0 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AMDAMD EPYC™ 9004 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ 7003 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ 9005 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ 8004 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ Embedded 7003 Series Processors | Affected– | Fixed in– |
| AMDAMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa") | Affected– | Fixed in– |
AI-suggested
- Apply firmware and microcode updates from AMD as soon as they become available to address this vulnerability.
- Enforce strict access controls and privilege separation on host systems to prevent unauthorized users from gaining the high-level privileges required to exploit this flaw.
- Limit the creation and management of SEV-ES guests to trusted administrators and monitor for anomalous VM creation activities.
- Employ runtime monitoring and integrity verification tools to detect suspicious behavior indicative of attempts to exploit SEV firmware vulnerabilities.
- Isolate sensitive workloads on hardware or environments not affected by this vulnerability until patches are applied.
- Engage with cloud service providers to understand their mitigation strategies if using third-party infrastructure.
- Conduct regular security audits and penetration testing focusing on virtualization security to identify potential privilege escalations.
- Maintain up-to-date incident response plans that include scenarios involving hardware-based virtualization attacks.
Description
Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.