amd epyc 7232p firmware
productUScpe:2.3:o:amd:epyc_7232p_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
4critical28high39medium1low
updated 2026-10-27
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2023-20593US | medium5.5OT elevated | 5.07% (92nd) | Exploit | ✗no fix | 2023-07-24 | — |
| CVE-2021-26322US | high7.5OT elevated | 1.05% (64th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2020-12988US | high7.5 | 1.04% (64th) | — | ✓romepi-sp3_1.0.0.c | 2021-06-11 | < romepi-sp3_1.0.0.c |
| CVE-2023-20592US | medium6.5 | 1.02% (63rd) | — | ✗no fix | 2023-11-14 | — |
| CVE-2021-26338US | high7.5 | 0.93% (60th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2023-20575US | medium6.5 | 0.80% (57th) | — | ✗no fix | 2023-07-11 | — |
| CVE-2023-20520US | critical9.8 | 0.79% (56th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.d |
| CVE-2021-46769US | high8.8 | 0.78% (56th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2021-26379US | critical9.8 | 0.68% (52nd) | — | ✓romepi_1.0.0.e | 2023-05-09 | < romepi_1.0.0.e |
| CVE-2021-46756US | critical9.1 | 0.65% (51st) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2023-20531US | high7.5 | 0.63% (50th) | — | ✓romepi_1.0.0.c | 2023-01-11 | < romepi_1.0.0.c |
| CVE-2023-20529US | high7.5 | 0.63% (50th) | — | ✓romepi_1.0.0.c | 2023-01-11 | < romepi_1.0.0.c |
| CVE-2021-46764US | high7.5 | 0.63% (50th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2023-20527US | medium6.5 | 0.61% (49th) | — | ✓romepi_1.0.0.c | 2023-01-11 | < romepi_1.0.0.c |
| CVE-2023-20525US | medium6.5 | 0.61% (49th) | — | ✓romepi_100d | 2023-01-11 | < romepi_100d |
| CVE-2023-20532US | medium5.3 | 0.57% (47th) | — | ✓romepi_1.0.0.c | 2023-01-11 | < romepi_1.0.0.c |
| CVE-2021-46774US | high7.5 | 0.51% (43rd) | — | ✓romepi_1.0.0.g | 2023-11-14 | < romepi_1.0.0.g |
| CVE-2023-20533US | high7.5 | 0.50% (43rd) | — | ✓romepi_1.0.0.d | 2023-11-14 | < romepi_1.0.0.d |
| CVE-2023-20524US | high7.5 | 0.49% (42nd) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.c |
| CVE-2021-46763US | high7.5 | 0.49% (42nd) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2021-26345US | medium4.9 | 0.43% (38th) | — | ✓romepi_1.0.0.f | 2023-11-14 | < romepi_1.0.0.f |
| CVE-2021-26406US | high7.5 | 0.42% (36th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.a |
| CVE-2021-26356US | high7.4 | 0.40% (34th) | — | ✓romepi_1.0.0.d | 2023-05-09 | < romepi_1.0.0.d |
| CVE-2021-46762US | critical9.1 | 0.35% (28th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2020-12944US | high7.8 | 0.35% (28th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-46744US | medium6.5 | 0.33% (27th) | — | ✗no fix | 2022-05-11 | — |
| CVE-2021-26341US | medium6.5 | 0.32% (25th) | — | ✗no fix | 2022-03-11 | — |
| CVE-2021-46775US | medium6.8 | 0.32% (25th) | — | ✗no fix | 2023-05-09 | = romepi_1.0.0.e |
| CVE-2020-12966US | medium5.5 | 0.31% (24th) | — | ✗no fix | 2022-02-04 | — |
| CVE-2023-20526US | medium4.6 | 0.31% (24th) | — | ✓romepi_1.0.0.d | 2023-11-14 | < romepi_1.0.0.d |
| CVE-2021-26335US | high7.8 | 0.29% (22nd) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26331US | high7.8 | 0.29% (22nd) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26401US | medium5.6 | 0.29% (22nd) | — | ✗no fix | 2022-03-11 | — |
| CVE-2022-27672US | medium4.7 | 0.28% (21st) | — | ✗no fix | 2023-03-01 | — |
| CVE-2021-26408US | high7.1 | 0.27% (19th) | — | ✓romepi-sp3_1.0.0.c | 2022-05-10 | < romepi-sp3_1.0.0.c |
| CVE-2021-26316US | high7.8 | 0.27% (19th) | — | ✓romepi_1.0.0.d | 2023-01-11 | < romepi_1.0.0.d |
| CVE-2023-20521US | medium5.7 | 0.26% (18th) | — | ✓romepi_1.0.0.d | 2023-11-14 | < romepi_1.0.0.d |
| CVE-2021-26326US | high7.8 | 0.26% (18th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26321US | medium5.5 | 0.25% (17th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2023-20528US | low2.4 | 0.25% (16th) | — | ✓romepi_1.0.0.c | 2023-01-11 | < romepi_1.0.0.c |
| CVE-2020-12961US | high7.8 | 0.25% (16th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26340US | high8.4 | 0.25% (16th) | — | ✗no fix | 2021-12-10 | — |
| CVE-2021-26312US | medium5.5 | 0.25% (16th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26323US | high7.8 | 0.25% (16th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26337US | medium5.5 | 0.24% (15th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-46778US | medium5.6 | 0.24% (15th) | — | ✗no fix | 2022-08-10 | — |
| CVE-2021-26370US | high7.1 | 0.23% (14th) | — | ✓romepi-sp3_1.0.0.c | 2022-05-10 | < romepi-sp3_1.0.0.c |
| CVE-2020-12954US | medium5.5 | 0.23% (14th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2020-12946US | high7.1 | 0.22% (13th) | — | ✓romepi-sp3_1.0.0.c | 2021-11-16 | < romepi-sp3_1.0.0.c |
| CVE-2021-26375US | medium5.5 | 0.22% (13th) | — | ✓romepi-sp3_1.0.0.d | 2022-05-11 | < romepi-sp3_1.0.0.d |
showing 50 of 72