Skip to content
Fencer Vulns
high 7.5

CVE-2021-26406 json

Insufficient validation in parsing Owner's Certificate Authority (OCA) certificates in SEV (AMD Secure Encrypted Virtualization) and SEV-ES…

published 2023-05-09 3 y ago modified 2026-06-17 4 mo ago also EUVD-2021-13212

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

Summary

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.

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
21 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

  • AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
  • AMD Ryzen™ 2000 Series Desktop Processors “Pinnacle Ridge”
  • AMD Ryzen™ 3000 Series Desktop Processors “Matisse” AM4
  • AMD AMD Ryzen™ 5000 Series Desktop Processors “Vermeer” AM4
  • AMD 2nd Gen AMD Ryzen™ Threadripper™ Processors “Colfax”
  • AMD 3rd Gen AMD Ryzen™ Threadripper™ Processors “Castle Peak” HEDT
  • AMD Ryzen™ Threadripper™ PRO Processors “Castle Peak” WS
  • AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
  • AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
  • AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
  • AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
  • AMD 1st Gen AMD EPYC™ Processors
  • AMD 2nd Gen AMD EPYC™ Processors

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.