CWE · MITRE source
CWE-670Always-Incorrect Control Flow Implementation
The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.
This weakness captures cases in which a particular code segment is always incorrect with respect to the algorithm that it is implementing. For example, if a C programmer intends to include multiple statements in a single block but does not include the enclosing braces (CWE-483), then the logic is always incorrect. This issue is in contrast to most weaknesses in which the code usually behaves correctly, except when it is externally manipulated in malicious ways.
Last updated: 04 July 2026 00:28 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: mostly · 1 mapping(s) from 1 framework(s): ASVS 5.0 1 (mostly)
NIST 800-53 r5 controls that address this weakness (0)AI
| 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-2024-32896 KEV | 10.0 | 7.8 | 0.0301 | 2024-06-13 |
CVE-2019-17192 | 7.0 | 9.8 | 0.0273 | 2019-10-05 |
CVE-2020-17466 | 7.0 | 9.8 | 0.0147 | 2020-08-11 |
CVE-2020-1914 | 7.0 | 9.8 | 0.0251 | 2020-10-08 |
CVE-2022-25745 | 7.0 | 9.8 | 0.0042 | 2023-04-13 |
CVE-2024-32971 | 7.0 | 9.0 | 0.0073 | 2024-05-02 |
CVE-2025-29312 | 7.0 | 9.1 | 0.0045 | 2025-03-24 |
CVE-2025-43359 | 7.0 | 9.8 | 0.0086 | 2025-09-15 |
CVE-2026-55276 | 7.0 | 9.1 | 0.0037 | 2026-06-29 |
CVE-2020-9425 | 6.0 | 7.5 | 0.1667 | 2020-03-20 |
CVE-2017-0604 | 5.5 | 7.8 | 0.0052 | 2017-05-12 |
CVE-2018-16766 | 5.5 | 8.8 | 0.0127 | 2018-09-10 |
CVE-2019-9946 | 5.5 | 7.5 | 0.0312 | 2019-04-02 |
CVE-2019-11412 | 5.5 | 7.5 | 0.0209 | 2019-04-22 |
CVE-2019-19729 | 5.5 | 7.5 | 0.0109 | 2019-12-11 |
CVE-2014-2686 | 5.5 | 7.5 | 0.0118 | 2020-01-09 |
CVE-2019-20430 | 5.5 | 7.5 | 0.0221 | 2020-01-27 |
CVE-2019-19324 | 5.5 | 7.5 | 0.0101 | 2020-03-20 |
CVE-2020-25603 | 5.5 | 7.8 | 0.0042 | 2020-09-23 |
CVE-2020-36277 | 5.5 | 7.5 | 0.0243 | 2021-03-11 |
CVE-2021-0517 | 5.5 | 7.5 | 0.0080 | 2021-06-21 |
CVE-2021-37604 | 5.5 | 7.5 | 0.0123 | 2021-08-05 |
CVE-2021-37605 | 5.5 | 7.5 | 0.0128 | 2021-08-05 |
CVE-2021-34767 | 5.5 | 7.4 | 0.0076 | 2021-09-23 |
CVE-2021-41153 | 5.5 | 8.7 | 0.0100 | 2021-10-18 |