cve.bz

CVE-2021-26403 amd

6.5 mediumEPSS 0.1%

Medium (6.5) in amd. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-26403 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-26403?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-26403?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-26403 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
amd:epyc_7001_firmwarebefore naplespi_1.0.0.e
amd:epyc_7251_firmwarebefore naplespi_1.0.0.e
amd:epyc_7261_firmwarebefore naplespi_1.0.0.e
amd:epyc_7281_firmwarebefore naplespi_1.0.0.e
amd:epyc_7301_firmwarebefore naplespi_1.0.0.e
amd:epyc_7351_firmwarebefore naplespi_1.0.0.e
amd:epyc_7351p_firmwarebefore naplespi_1.0.0.e
amd:epyc_7371_firmwarebefore naplespi_1.0.0.e
amd:epyc_7401_firmwarebefore naplespi_1.0.0.e
amd:epyc_7401p_firmwarebefore naplespi_1.0.0.e
amd:epyc_7451_firmwarebefore naplespi_1.0.0.e
amd:epyc_7501_firmwarebefore naplespi_1.0.0.e
amd:epyc_7551_firmwarebefore naplespi_1.0.0.e
amd:epyc_7551p_firmwarebefore naplespi_1.0.0.e
amd:epyc_7601_firmwarebefore naplespi_1.0.0.e
amd:epyc_7002_firmwarebefore romepi_1.0.0.9
amd:epyc_7232p_firmwarebefore romepi_1.0.0.9
amd:epyc_7252_firmwarebefore romepi_1.0.0.9
amd:epyc_7262_firmwarebefore romepi_1.0.0.9
amd:epyc_7272_firmwarebefore romepi_1.0.0.9
amd:epyc_7282_firmwarebefore romepi_1.0.0.9
amd:epyc_7302_firmwarebefore romepi_1.0.0.9
amd:epyc_7302p_firmwarebefore romepi_1.0.0.9
amd:epyc_7352_firmwarebefore romepi_1.0.0.9
amd:epyc_7402_firmwarebefore romepi_1.0.0.9
amd:epyc_7402p_firmwarebefore romepi_1.0.0.9
amd:epyc_7452_firmwarebefore romepi_1.0.0.9
amd:epyc_7502_firmwarebefore romepi_1.0.0.9
amd:epyc_7502p_firmwarebefore romepi_1.0.0.9
amd:epyc_7532_firmwarebefore romepi_1.0.0.9
amd:epyc_7542_firmwarebefore romepi_1.0.0.9
amd:epyc_7552_firmwarebefore romepi_1.0.0.9
amd:epyc_7642_firmwarebefore romepi_1.0.0.9
amd:epyc_7662_firmwarebefore romepi_1.0.0.9
amd:epyc_7702_firmwarebefore romepi_1.0.0.9
amd:epyc_7702p_firmwarebefore romepi_1.0.0.9
amd:epyc_7742_firmwarebefore romepi_1.0.0.9
amd:epyc_7f32_firmwarebefore romepi_1.0.0.9
amd:epyc_7f52_firmwarebefore romepi_1.0.0.9
amd:epyc_7f72_firmwarebefore romepi_1.0.0.9
amd:epyc_7h12_firmwarebefore romepi_1.0.0.9

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON