CWE · MITRE source
CWE-180Incorrect Behavior Order: Validate Before Canonicalize
The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.
This can be used by an attacker to bypass the validation and launch attacks that expose weaknesses that would otherwise be prevented, such as injection.
Last updated: 21 August 2026 14:15 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 · 6 mapping(s) from 1 framework(s): CAPEC 6 (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. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-26136 UPD | 7.9 | 9.8 | 0.0502 | 2022-07-20 |
CVE-2026-24895 UPD | 7.4 | 9.8 | 0.0057 | 2026-02-12 |
CVE-2026-27590 | 7.3 | 9.8 | 0.0054 | 2026-02-24 |
CVE-2026-15704 | 7.2 | 9.8 | 0.0035 | 2026-07-24 |
CVE-2022-26137 UPD | 6.9 | 8.8 | 0.0220 | 2022-07-20 |
CVE-2026-52747 | 6.3 | 8.6 | 0.0052 | 2026-07-10 |
CVE-2026-39364 UPD | 6.2 | 7.5 | 0.0209 | 2026-04-07 |
CVE-2026-48721 | 5.8 | 8.6 | 0.0014 | 2026-06-24 |
CVE-2026-49984 | 5.7 | 7.7 | 0.0046 | 2026-06-26 |
CVE-2026-45022 UPD | 5.6 | 7.5 | 0.0016 | 2026-05-27 |
CVE-2026-62999 | 5.6 | 7.5 | 0.0029 | 2026-07-31 |
CVE-2026-42462 | 5.2 | 7.0 | 0.0017 | 2026-06-10 |
CVE-2026-69246 | 5.2 | 7.2 | 0.0021 | 2026-08-03 |
CVE-2026-69245 | 4.9 | 6.5 | 0.0014 | 2026-08-03 |
CVE-2025-43716 UPD | 4.8 | 5.8 | 0.0118 | 2025-04-23 |
CVE-2026-72917 | 4.6 | 5.9 | 0.0027 | 2026-08-10 |
CVE-2026-39409 UPD | 4.4 | 5.3 | 0.0034 | 2026-04-08 |
CVE-2026-34786 UPD | 4.3 | 5.3 | 0.0019 | 2026-04-02 |
CVE-2026-7120 | 4.3 | 5.3 | 0.0022 | 2026-07-23 |
CVE-2025-33194 UPD | 4.1 | 5.7 | 0.0015 | 2025-11-25 |
CVE-2026-34475 UPD | 4.0 | 5.4 | 0.0020 | 2026-03-27 |
CVE-2024-28607 UPD | 2.5 | 2.9 | 0.0015 | 2025-03-11 |