2nd Gen AMD EPYC™ Processors
AMD
- Product type
- Other
- Catalog vulnerabilities
- 19
Severity across 19 analyzed records
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
As of 09/13/2026, within CyStack's analyzed data, 2nd Gen AMD EPYC™ Processors has 1 security vulnerability published in the last 90 days. Of these, 1 is rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of 2nd Gen AMD EPYC™ Processors and determine which vulnerabilities affect that version.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScanVerify to analyze this security profile
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2023-20577 | Exploitation statusNot known exploited | FixNot confirmed | Published09/02/2026 | SeverityHigh |
CVE-2023-31315 | Exploitation statusNot known exploited | FixYes | Published08/09/2024 | SeverityHigh |
CVE-2022-23829 | Exploitation statusNot known exploited | FixNot confirmed | Published06/18/2024 | SeverityHigh |
CVE-2023-20587 | Exploitation statusNot known exploited | FixNot confirmed | Published02/13/2024 | SeverityHigh |
CVE-2023-20592 | Exploitation statusNot known exploited | FixNot confirmed | Published11/14/2023 | SeverityUnknown |
CVE-2021-26345 | Exploitation statusNot confirmed | FixNot confirmed | Published11/14/2023 | SeverityLow |
CVE-2023-20533 | Exploitation statusNot confirmed | FixNot confirmed | Published11/14/2023 | SeverityMedium |
CVE-2023-20526 | Exploitation statusNot confirmed | FixNot confirmed | Published11/14/2023 | SeverityLow |
CVE-2023-20521 | Exploitation statusNot known exploited | FixNot confirmed | Published11/14/2023 | SeverityLow |
CVE-2021-46774 | Exploitation statusNot known exploited | FixNot confirmed | Published11/14/2023 | SeverityMedium |
CVE-2023-20569 | Exploitation statusNot confirmed | FixNot confirmed | Published08/08/2023 | SeverityUnknown |
CVE-2023-20593 | Exploitation statusPublic exploit | FixNot confirmed | Published07/24/2023 | SeverityUnknown |
CVE-2023-20575 | Exploitation statusNot known exploited | FixNot confirmed | Published07/11/2023 | SeverityMedium |
CVE-2021-46756 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityCritical |
CVE-2021-26406 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityHigh |
CVE-2021-26371 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityMedium |
CVE-2021-26356 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityHigh |
CVE-2021-26354 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityMedium |
CVE-2022-27672 | Exploitation statusNot confirmed | FixNot confirmed | Published02/14/2023 | SeverityUnknown |
