CWE · MITRE source
CWE-691Insufficient Control Flow Management
The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected 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 · 19 mapping(s) from 4 framework(s): ATT&CK 16 (mostly) · CAPEC 1 (partial) · STIG windows 10 1 (partial) · STIG windows 11 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SA-24 | Design For Cyber Resiliency | SA | Design principles and implementation approaches enforce robust control-flow management to maintain function and enable recovery after disruption. |
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). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2021-4106 | 5.5 | 7.8 | 0.0025 | 2022-02-16 |
CVE-2022-20697 | 5.5 | 8.6 | 0.0111 | 2022-04-15 |
CVE-2023-20559 | 5.5 | 8.8 | 0.0067 | 2023-04-02 |
CVE-2021-33157 | 5.5 | 7.2 | 0.0020 | 2024-02-23 |
CVE-2024-21801 | 5.5 | 7.1 | 0.0018 | 2024-08-14 |
CVE-2025-20004 UPD | 5.5 | 7.2 | 0.0013 | 2025-05-13 |
CVE-2025-22893 UPD | 5.5 | 7.8 | 0.0012 | 2025-08-12 |
CVE-2025-24305 UPD | 5.5 | 7.2 | 0.0013 | 2025-08-12 |
CVE-2025-25273 UPD | 5.5 | 7.8 | 0.0012 | 2025-08-12 |
CVE-2025-35963 | 5.5 | 7.4 | 0.0016 | 2025-11-11 |
CVE-2022-46828 | 3.5 | 5.2 | 0.0027 | 2022-12-08 |
CVE-2022-48481 | 3.5 | 5.2 | 0.0021 | 2023-04-28 |
CVE-2022-37409 | 3.5 | 4.7 | 0.0017 | 2023-05-10 |
CVE-2022-41646 | 3.5 | 4.7 | 0.0017 | 2023-05-10 |
CVE-2022-43505 | 3.5 | 4.1 | 0.0016 | 2023-08-11 |
CVE-2023-28711 | 3.5 | 5.5 | 0.0016 | 2023-08-11 |
CVE-2023-44384 | 3.5 | 4.1 | 0.0043 | 2023-10-06 |
CVE-2023-5102 | 3.5 | 5.3 | 0.0057 | 2023-10-09 |
CVE-2023-24587 | 3.5 | 6.9 | 0.0018 | 2023-11-14 |
CVE-2024-3847 | 3.5 | 6.1 | 0.0080 | 2024-04-17 |
CVE-2024-22374 | 3.5 | 6.5 | 0.0016 | 2024-08-14 |
CVE-2024-29079 | 3.5 | 6.8 | 0.0020 | 2024-11-13 |
CVE-2024-33617 | 3.5 | 5.9 | 0.0045 | 2024-11-13 |
CVE-2025-25774 | 3.5 | 6.5 | 0.0039 | 2025-03-12 |
CVE-2025-20022 UPD | 3.5 | 5.7 | 0.0019 | 2025-05-13 |