CVE-2021-26391: Insufficient verification of multiple header signatures while loading a Trusted Application (TA) may allow an attacker with privileges to…
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.19% (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
Insufficient verification of multiple header signatures while loading a Trusted Application (TA) may allow an attacker with privileges to gain code execution in that TA or the OS/kernel.
- Published
- Nov 9, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-347
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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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 | enterprise driver | cpe:2.3:a:amd:enterprise_driver |
| amd | radeon pro software | cpe:2.3:a:amd:radeon_pro_software |
| amd | radeon software | cpe:2.3:a:amd:radeon_software |
| amd | radeon pro w5500 | cpe:2.3:h:amd:radeon_pro_w5500 |
| amd | radeon pro w5500x | cpe:2.3:h:amd:radeon_pro_w5500x |
| amd | radeon pro w5700 | cpe:2.3:h:amd:radeon_pro_w5700 |
| amd | radeon pro w5700x | cpe:2.3:h:amd:radeon_pro_w5700x |
| amd | radeon pro w6300m | cpe:2.3:h:amd:radeon_pro_w6300m |
| amd | radeon pro w6400 | cpe:2.3:h:amd:radeon_pro_w6400 |
| amd | radeon pro w6500m | cpe:2.3:h:amd:radeon_pro_w6500m |
| amd | radeon pro w6600 | cpe:2.3:h:amd:radeon_pro_w6600 |
| amd | radeon pro w6600m | cpe:2.3:h:amd:radeon_pro_w6600m |
and 86 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 AMD Radeon RX 5000 Series & PRO W5000 Series
- AMD Radeon Software and later · before 22.5.2affected
- AMD Radeon Pro Software Enterprise and later · before 22.Q2affected
- Enterprise Driver and later · before 22.10.20affected
AMD AMD Radeon RX 6000 Series & PRO W6000 Series
- AMD Radeon Software and later · before 22.5.2affected
- AMD Radeon Pro Software Enterprise and later · before 22.Q2affected
- Enterprise Driver and later · before 22.10.20affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd enterprise driverbefore 22.10.20
- amd radeon pro softwarebefore 22.q2
- amd radeon rx vega 56 firmwareall versions
- amd radeon rx vega 64 firmwareall versions
- amd radeon softwarebefore 22.5.2
- amd ryzen 3 5300g firmwareall versions
- amd ryzen 3 5300ge firmwareall versions
- amd ryzen 3 5300u firmwareall versions
- amd ryzen 3 5400u firmwareall versions
- amd ryzen 5 5500u firmwareall versions
- amd ryzen 5 5560u firmwareall versions
- amd ryzen 5 5600g firmwareall versions
- amd ryzen 5 5600ge firmwareall versions
- amd ryzen 5 5600h firmwareall versions
- amd ryzen 5 5600hs firmwareall versions
- amd ryzen 5 5600u firmwareall versions
- amd ryzen 7 5700g firmwareall versions
- amd ryzen 7 5700ge firmwareall versions
- amd ryzen 7 5700u firmwareall versions
- amd ryzen 7 5800h firmwareall versions
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26392Insufficient verification of missing size check in 'LoadModule' may lead to an out-of-bounds write potentially allowing an attacker with…31Monitor
- CVE-2021-26360An attacker with local access to the system can make unauthorized modifications of the security configuration of the SOC registers.31Monitor
- CVE-2020-12931Improper parameters handling in the AMD Secure Processor (ASP) kernel may allow a privileged attacker to elevate their privileges…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-12930Nov 9, 2022 · Improper parameters handling in AMD Secure Processor (ASP) drivers may allow a privileged attacker to elevate their privileges potentially…31Monitor
- Later →CVE-2021-26393Nov 9, 2022 · Insufficient memory cleanup in the AMD Secure Processor (ASP) Trusted Execution Environment (TEE) may allow an authenticated attacker with…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-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});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)
ATT&CK techniques
—
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.