Skip to main content
VulnerabilityPublished

CVE-2025-48514: AMD EPYC™ 9004 Series Processors · Insufficient Granularity of Access Control

Affects AMD EPYC™ 9004 Series ProcessorsSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
AMDAMD EPYC™ 9004 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 7003 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 9005 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ 8004 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 7003 Series ProcessorsAffected–Fixed in–
AMDAMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa")Affected–Fixed in–

AI-suggested

  1. Apply firmware and microcode updates from AMD as soon as they become available to address this vulnerability.
  2. 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.
  3. Limit the creation and management of SEV-ES guests to trusted administrators and monitor for anomalous VM creation activities.
  4. Employ runtime monitoring and integrity verification tools to detect suspicious behavior indicative of attempts to exploit SEV firmware vulnerabilities.
  5. Isolate sensitive workloads on hardware or environments not affected by this vulnerability until patches are applied.
  6. Engage with cloud service providers to understand their mitigation strategies if using third-party infrastructure.
  7. Conduct regular security audits and penetration testing focusing on virtualization security to identify potential privilege escalations.
  8. 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.

References

Community reviews

Loading reviews…