CWE · MITRE source
CWE-1270Generation of Incorrect Security Tokens
The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.
Systems-On-a-Chip (SoC) (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify actions originated from various agents. These actions could be "read", "write", "program", "reset", "fetch", "compute", etc. Security Tokens are generated and assigned to every agent on the SoC that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Token based on its trust level or privileges.
Last updated: 20 August 2026 13:14 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 1 framework(s): CAPEC 2 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-31122 UPD | 7.4 | 9.8 | 0.0064 | 2022-10-18 |
CVE-2023-2882 UPD | 7.4 | 9.8 | 0.0064 | 2023-05-25 |
CVE-2026-49499 UPD | 6.4 | 8.8 | 0.0029 | 2026-07-22 |
CVE-2026-54593 | 6.1 | 8.1 | 0.0036 | 2026-07-28 |
CVE-2025-59698 | 5.1 | 6.8 | 0.0029 | 2025-12-02 |
CVE-2023-22644 UPD | 4.4 | 5.5 | 0.0045 | 2023-09-20 |
CVE-2026-19636 | 4.1 | 5.3 | 0.0026 | 2026-08-14 |
CVE-2023-30524 UPD | 3.7 | 4.3 | 0.0043 | 2023-04-12 |
CVE-2026-15831 | 3.6 | 4.3 | 0.0022 | 2026-07-29 |