Skip to content
Fencer Vulns
medium 6.5

CVE-2021-26403 json

Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confid…

published 2023-01-10 3 y ago modified 2026-06-17 4 mo ago also EUVD-2021-13209

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confidentiality.

Patch / fix

  • amd epyc_7001_firmware naplespi_1.0.0.e
  • amd epyc_7251_firmware naplespi_1.0.0.e
  • amd epyc_7261_firmware naplespi_1.0.0.e
  • amd epyc_7281_firmware naplespi_1.0.0.e
  • amd epyc_7301_firmware naplespi_1.0.0.e
  • amd epyc_7351_firmware naplespi_1.0.0.e
  • amd epyc_7351p_firmware naplespi_1.0.0.e
  • amd epyc_7371_firmware naplespi_1.0.0.e
  • amd epyc_7401_firmware naplespi_1.0.0.e
  • amd epyc_7401p_firmware naplespi_1.0.0.e
  • amd epyc_7451_firmware naplespi_1.0.0.e
  • amd epyc_7501_firmware naplespi_1.0.0.e
  • amd epyc_7551_firmware naplespi_1.0.0.e
  • amd epyc_7551p_firmware naplespi_1.0.0.e
  • amd epyc_7601_firmware naplespi_1.0.0.e
  • amd epyc_7002_firmware romepi_1.0.0.9
  • amd epyc_7232p_firmware romepi_1.0.0.9
  • amd epyc_7252_firmware romepi_1.0.0.9
  • amd epyc_7262_firmware romepi_1.0.0.9
  • amd epyc_7272_firmware romepi_1.0.0.9

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected products

  • AMD 1st Gen EPYC
  • AMD 2nd Gen EPYC

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.