voxell vciy
CVE-2021-26326
ROUTINE
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: epyc milanpi-sp3_1.0.0.4; epyc 7232p firmware romepi-sp3_1.0.0.c; epyc 72f3 firmware milanpi-sp3_1.0.0.4; epyc 7313p firmware milanpi-sp3_1.0.0.4; epyc 73f3 firmware milanpi-sp3_1.0.0.4… upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Failure to validate VM_HSAVE_PA during SNP_INIT may result in a loss of memory integrity.
- weakness
- CWE-665 Improper Initialization
- affected
- AMD 3rd Gen AMD EPYC™
- published ranges
- amd epyc 7232p firmware < romepi-sp3_1.0.0.c; amd epyc 7763 firmware < milanpi-sp3_1.0.0.4; amd epyc 7713p firmware < milanpi-sp3_1.0.0.4; amd epyc 7713 firmware < milanpi-sp3_1.0.0.4; and 16 more on the CVE page
- first unaffected version, by branch
- epyc milanpi-sp3_1.0.0.4; epyc 7232p firmware romepi-sp3_1.0.0.c; epyc 72f3 firmware milanpi-sp3_1.0.0.4; epyc 7313p firmware milanpi-sp3_1.0.0.4; epyc 73f3 firmware milanpi-sp3_1.0.0.4…
- assigned by
- AMD
- published
- 2021-11-16
check us amd.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 17 Nov 2021 | 0.00416 | |
| 6 Jan 2022 | 0.0184 | |
| 4 Feb 2022 | 0.01404 | |
| 1 Apr 2022 | 0.00885 | |
| 7 Mar 2023 | 0.00043 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.00108 | scoring model v2025.03.14 |
| 12 Jun 2025 | 0.00046 | |
| 13 Apr 2026 | 0.00127 | |
| 15 Jun 2026 | 0.00253 | scoring model v2026.06.15 |
| 9 Sep 2026 | 0.00261 |
18 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-09 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: epyc milanpi-sp3_1.0.0.4; epyc 7232p firmware romepi-sp3_1.0.0.c; epyc 72f3 firmware milanpi-sp3_1.0.0.4; epyc 7313p firmware milanpi-sp3_1.0.0.4; epyc 73f3 firmware milanpi-sp3_1.0.0.4…. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-26326', '2026-11-01T23:59:59.999999Z', now());