CVE-2021-26315: When the AMD Platform Security Processor (PSP) boot rom loads, authenticates, and subsequently decrypts an encrypted FW, due to insufficient…
Noroxi assessment
Priority: Monitor (action score 31/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- 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
When the AMD Platform Security Processor (PSP) boot rom loads, authenticates, and subsequently decrypts an encrypted FW, due to insufficient verification of the integrity of decrypted image, arbitrary code may be executed in the PSP when encrypted firmware images are used.
- Published
- Nov 16, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-345
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 7003 firmware | cpe:2.3:o:amd:epyc_7003_firmware |
| amd | epyc 7003 | cpe:2.3:h:amd:epyc_7003 |
| amd | epyc 72f3 firmware | cpe:2.3:o:amd:epyc_72f3_firmware |
| amd | epyc 72f3 | cpe:2.3:h:amd:epyc_72f3 |
| amd | epyc 7313 firmware | cpe:2.3:o:amd:epyc_7313_firmware |
| amd | epyc 7313 | cpe:2.3:h:amd:epyc_7313 |
| amd | epyc 7313p firmware | cpe:2.3:o:amd:epyc_7313p_firmware |
| amd | epyc 7313p | cpe:2.3:h:amd:epyc_7313p |
| amd | epyc 7343 firmware | cpe:2.3:o:amd:epyc_7343_firmware |
| amd | epyc 7343 | cpe:2.3:h:amd:epyc_7343 |
| amd | epyc 73f3 firmware | cpe:2.3:o:amd:epyc_73f3_firmware |
| amd | epyc 73f3 | cpe:2.3:h:amd:epyc_73f3 |
and 28 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 3rd Gen AMD EPYC™
- unspecified and later · before MilanPI-SP3_1.0.0.4affected
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 7003 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 72f3 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7313 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7313p firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7343 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 73f3 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7413 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7443 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7443p firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7453 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 74f3 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7513 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7543 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7543p firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 75f3 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7643 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7663 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7713 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7713p firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7763 firmwarebefore milanpi-sp3_1.0.0.4
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26335Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use…31Monitor
- CVE-2021-26331AMD System Management Unit (SMU) contains a potential issue where a malicious user may be able to manipulate mailbox entries leading to…31Monitor
- CVE-2020-12961A potential vulnerability exists in AMD Platform Security Processor (PSP) that may allow an attacker to zero any privileged register on the…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-12951Nov 16, 2021 · Race condition in ASP firmware could allow less privileged x86 code to perform ASP SMM (System Management Mode) operations.28Monitor
- ← EarlierCVE-2020-12954Nov 16, 2021 · A side effect of an integrated chipset option may be able to be used by an attacker to bypass SPI ROM protections, allowing unauthorized…22Monitor
- Later →CVE-2021-26327Nov 16, 2021 · Insufficient validation of guest context in the SNP Firmware could lead to a potential loss of guest confidentiality.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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.