CVE-2021-26406: Insufficient validation in parsing Owner's Certificate Authority (OCA) certificates in SEV (AMD Secure Encrypted Virtualization) and SEV-ES…
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Insufficient validation in parsing Owner's Certificate Authority (OCA) certificates in SEV (AMD Secure Encrypted Virtualization) and SEV-ES user application can lead to a host crash potentially resulting in denial of service.
- Published
- May 9, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- —
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 7232p firmware | cpe:2.3:o:amd:epyc_7232p_firmware |
| amd | epyc 7232p | cpe:2.3:h:amd:epyc_7232p |
| amd | epyc 7252 firmware | cpe:2.3:o:amd:epyc_7252_firmware |
| amd | epyc 7252 | cpe:2.3:h:amd:epyc_7252 |
| amd | epyc 7262 firmware | cpe:2.3:o:amd:epyc_7262_firmware |
| amd | epyc 7262 | cpe:2.3:h:amd:epyc_7262 |
| amd | epyc 7272 firmware | cpe:2.3:o:amd:epyc_7272_firmware |
| amd | epyc 7272 | cpe:2.3:h:amd:epyc_7272 |
| amd | epyc 7282 firmware | cpe:2.3:o:amd:epyc_7282_firmware |
| amd | epyc 7282 | cpe:2.3:h:amd:epyc_7282 |
| amd | epyc 7302 firmware | cpe:2.3:o:amd:epyc_7302_firmware |
| amd | epyc 7302 | cpe:2.3:h:amd:epyc_7302 |
and 68 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD 1st Gen AMD EPYC™ Processors
- variousaffected
AMD 2nd Gen AMD EPYC™ Processors
- variousaffected
AMD 2nd Gen AMD Ryzen™ Threadripper™ Processors “Colfax”
- variousaffected
AMD 3rd Gen AMD Ryzen™ Threadripper™ Processors “Castle Peak” HEDT
- variousaffected
AMD AMD Ryzen™ 5000 Series Desktop Processors “Vermeer” AM4
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
- variousaffected
AMD Ryzen™ 2000 Series Desktop Processors “Pinnacle Ridge”
- variousaffected
AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
- variousaffected
AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
- variousaffected
AMD Ryzen™ 3000 Series Desktop Processors “Matisse” AM4
- variousaffected
AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7232p firmwareromepi_1.0.0.a
- amd epyc 7251 firmwarenaplespi_1.0.0.e
- amd epyc 7252 firmwareromepi_1.0.0.a
- amd epyc 7261 firmwarenaplespi_1.0.0.e
- amd epyc 7262 firmwareromepi_1.0.0.a
- amd epyc 7272 firmwareromepi_1.0.0.a
- amd epyc 7281 firmwarenaplespi_1.0.0.e
- amd epyc 7282 firmwareromepi_1.0.0.a
- amd epyc 7301 firmwarenaplespi_1.0.0.e
- amd epyc 7302 firmwareromepi_1.0.0.a
- amd epyc 7302p firmwareromepi_1.0.0.a
- amd epyc 7351 firmwarenaplespi_1.0.0.e
- amd epyc 7351p firmwarenaplespi_1.0.0.e
- amd epyc 7352 firmwareromepi_1.0.0.a
- amd epyc 7371 firmwarenaplespi_1.0.0.e
- amd epyc 7401 firmwarenaplespi_1.0.0.e
- amd epyc 7401p firmwarenaplespi_1.0.0.e
- amd epyc 7402 firmwareromepi_1.0.0.a
- amd epyc 7402p firmwareromepi_1.0.0.a
- amd epyc 7451 firmwarenaplespi_1.0.0.e
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26323Failure to validate SEV Commands while SNP is active may result in a potential impact to memory integrity.31Monitor
- CVE-2021-26326Failure to validate VM_HSAVE_PA during SNP_INIT may result in a loss of memory integrity.31Monitor
- CVE-2023-20533Insufficient DRAM address validation in System
Management Unit (SMU) may allow an attacker to read/write from/to an invalid
DRAM address…30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26376May 11, 2022 · Insufficient checks in System Management Unit (SMU) FeatureConfig may result in reenabling features potentially resulting in denial of…22Monitor
- ← EarlierCVE-2021-26378May 11, 2022 · Insufficient bound checks in the System Management Unit (SMU) may result in access to an invalid address space that could result in denial…22Monitor
- ← EarlierCVE-2021-26388May 11, 2022 · Improper validation of the BIOS directory may allow for searches to read beyond the directory table copy in RAM, exposing out of bounds…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.