MITRE has released CWE 5.0. The catalogue is dated 28 October 2026, and it is the first major version since the 4.x line began.[1] The TLCTC CWE mapping now follows it: 1,012 entries, every one of the 984 weaknesses in CWE 5.0 plus 28 other identifiers that real data still cites.[2]
Fifteen weaknesses are new. None of them needed an eleventh cluster. Seven of them are #4, and there is a reason for that.
What changed in CWE 5.0
- 15 new weaknesses (CWE-1461 to CWE-1467 and CWE-1469 to CWE-1476; CWE-1468 is a view).
- 3 weaknesses deprecated: CWE-377 Insecure Temporary File, CWE-391 Unchecked Error Condition and CWE-613 Insufficient Session Expiration. CWE-613 was split into a new session-management family.
- Names without nicknames. 45 weakness names lost the common name they carried in parentheses. “SQL Injection” is no longer part of CWE-89’s name; it moved to the alternate terms.
- Structure. Categories became
Groupingelements in a new schema (v8.0), with the same identifiers. 20 abstraction levels and 39 parent links changed, and there are 4 new views. - Usage guidance. CWE-787 Out-of-bounds Write moved from Allowed to Allowed-with-Review for vulnerability mapping.
Where the fifteen new weaknesses land
Each new weakness was classified by the generic vulnerability it describes, with the same decision tree as the other thousand entries.[3]
| CWE | Name | TLCTC |
|---|---|---|
| CWE-1462 | Improper Session Management (parent, Discouraged) | #4 |
| CWE-1463 | Insufficient Session Timeout Value | #4 |
| CWE-1464 | Improper Session Invalidation | #4 |
| CWE-1465 | Improper Session Invalidation after User Logout | #4 |
| CWE-1466 | Improper Session Invalidation after Authentication Credential Change | #4 |
| CWE-1467 | Use of Singular Authentication Artifact for Multiple User Sessions | #4 |
| CWE-1469 | Improper Check for Credential Expiration | #4 |
| CWE-1470 | Improper External Identity Verification | #1 |
| CWE-1471 | Insufficiently Controlled Parser Differential | #2 | #3 |
| CWE-1474 | Non-Equivalent Data Transformation | #2 | #3 |
| CWE-1475 | Incomplete Data/State Propagation | #2 | #3 |
| CWE-1461 | Hardware Simulation / Synthesis Mismatch | #2 |
| CWE-1476 | Improper Request Propagation before Data Reception in Write Transactions in a Bus Architecture | #2 |
| CWE-1472 | Generation of Credential with Long Expiration | enabling condition |
| CWE-1473 | Improper Expiration of Cached Data | N/A (too abstract) |
#2 | #3 means the cluster follows the role of the flawed component (R-ROLE): server-role code is #2, client-role code is #3. The two hardware-logic weaknesses are #2 because the flaw is in implemented logic, not in a physical property of the substrate (R-SPECIFIC).
Why seven of them are #4
The generic vulnerability of #4 Identity Theft is insufficient binding, at the point of authentication, between a presented credential and the authentic holder of the identity it claims.[4] Read the new session family against that sentence:
- A session that never times out, or survives logout or a password change, is still accepted after its holder has gone.
- One authentication artifact shared by every session proves nothing about which holder is present.
- An expired credential that is not checked is still accepted.
Each describes the same gap: what is presented is accepted, although it no longer binds to the person behind it. CWE 5.0 now names that gap in seven entries. TLCTC already had one place for it.
Two neighbours that are not #4. CWE-1472, a credential generated with a long lifetime, is accepted correctly while it is valid. Its weakness is the window it opens for later misuse, so it is recorded as an enabling condition, not a cluster. CWE-1470, an enrolment or account-linking function that accepts an email address or phone number without checking that the user controls it, is #1 Abuse of Functions: the flaw sits in the function that creates the binding, not at the point where a credential is presented.
Common names stay searchable
Practitioners still say “SQL injection”, not “Improper Neutralization of Special Elements used in an SQL Command”. The mapping now carries an optional field, cweCommonNames, on 53 records with 78 terms: the alternate terms CWE 5.0 marks as common names, acronyms or abbreviations, and the common name a title carried before 5.0. The CWE Explorer searches them, so “SQLi” still finds CWE-89. Tools that read the JSON and do not know the field can ignore it.
What we corrected on the way
Comparing every identifier against the 5.0 catalogue also turned up errors of our own:
- CWE-1305 was an invented record. Our file described it as a memory-decoding weakness mapped to #2. The identifier is the view “CISQ Quality Measures (2020)”. It is now
N/A, Prohibited, like every view. - CWE-21, a deprecated category, was still mapped to #2 | #3. It is now
N/A, Prohibited, as are the three weaknesses deprecated in 5.0. They stay in the file so that old references still resolve. - The count. Earlier pages said “985 weaknesses”. That number counted entries, not weaknesses, and not every entry maps to a cluster. The file went from 985 entries to 997 on 11 November when four missing weaknesses and eight categories cited in the KEV catalogue were added, and to 1,012 with CWE 5.0. Every site page now uses the current count.
The numbers
| Measure | CWE 5.0 mapping |
|---|---|
| Entries | 1,012 (984 weaknesses + 28 other identifiers) |
| Mapped to a cluster | 791 |
| Enabling condition (no cluster of its own) | 22 |
| N/A (views, categories, deprecated, too abstract) | 199 |
| Verdicts: Allowed / Allowed-with-Review / Discouraged / Prohibited | 735 / 46 / 174 / 57 |
| Context-dependent | 265, of which 230 are decided by R-ROLE |
What did not change: the ten clusters, the decision tree and the KEV overlay. A new catalogue version added weaknesses; it did not add a new kind of cause. That is what a top level should be able to absorb.
The mapping is AI-generated and human-reviewed, and it has not been independently validated. Treat it as experimental. Corrections are welcome on GitHub.
Sources
- [1] MITRE, Common Weakness Enumeration, CWE List version 5.0 (catalogue
cwec_v5.0.xml, dated 28 October 2026). - [2] TLCTC CWE mapping on GitHub:
mappings/mitre-cwe/tlctc-cwe.json(CWE 5.0, 1,012 entries), and the TLCTC CWE Explorer. - [3] TLCTC & CWE Mapping: Context is King (TLCTC blog), and the CWE decision tree.
- [4] TLCTC v2.7 core paper, cluster definitions, R-ROLE, R-SPECIFIC; The 10 Clusters.
- [5] Time for a Reboot: Why MITRE CWE Needs Taxonomic Discipline (TLCTC blog, December 2025).
TLCTC Framework · v2.7 · CC BY 4.0