CWE · MITRE source
CWE-834Excessive Iteration
The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.
If the iteration can be influenced by an attacker, this weakness could allow attackers to consume excessive resources such as CPU or memory. In many cases, a loop does not need to be infinite in order to cause enough resource consumption to adversely affect the product or its host system; it depends on the amount of resources consumed per iteration.
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 · 2 mapping(s) from 1 framework(s): ATT&CK 2 (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. | |||
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-35515 | 6.0 | 7.5 | 0.1188 | 2021-07-13 |
CVE-2017-11188 | 5.5 | 7.5 | 0.0155 | 2017-07-12 |
CVE-2017-11409 | 5.5 | 7.5 | 0.0226 | 2017-07-18 |
CVE-2017-12587 | 5.5 | 8.8 | 0.0203 | 2017-08-06 |
CVE-2018-7321 | 5.5 | 7.5 | 0.0171 | 2018-02-23 |
CVE-2018-7323 | 5.5 | 7.5 | 0.0245 | 2018-02-23 |
CVE-2018-9261 | 5.5 | 7.5 | 0.0294 | 2018-04-04 |
CVE-2018-11813 | 5.5 | 7.5 | 0.0316 | 2018-06-06 |
CVE-2018-14342 | 5.5 | 7.5 | 0.0370 | 2018-07-19 |
CVE-2019-3552 | 5.5 | 7.5 | 0.0198 | 2019-05-06 |
CVE-2019-3558 | 5.5 | 7.5 | 0.0202 | 2019-05-06 |
CVE-2019-3559 | 5.5 | 7.5 | 0.0199 | 2019-05-06 |
CVE-2019-3564 | 5.5 | 7.5 | 0.0199 | 2019-05-06 |
CVE-2019-3565 | 5.5 | 7.5 | 0.0281 | 2019-05-06 |
CVE-2020-14303 | 5.5 | 7.5 | 0.0354 | 2020-07-06 |
CVE-2020-35573 | 5.5 | 7.5 | 0.0266 | 2020-12-20 |
CVE-2021-23270 | 5.5 | 7.5 | 0.0103 | 2021-04-12 |
CVE-2021-3125 | 5.5 | 7.5 | 0.0150 | 2021-04-12 |
CVE-2021-3128 | 5.5 | 7.5 | 0.0218 | 2021-04-12 |
CVE-2021-39204 | 5.5 | 7.5 | 0.0166 | 2021-09-09 |
CVE-2021-39923 | 5.5 | 7.5 | 0.0152 | 2021-11-19 |
CVE-2021-39924 | 5.5 | 7.5 | 0.0493 | 2021-11-19 |
CVE-2021-4190 | 5.5 | 7.5 | 0.0310 | 2021-12-30 |
CVE-2021-4021 | 5.5 | 7.5 | 0.0103 | 2022-02-24 |
CVE-2023-26513 | 5.5 | 7.5 | 0.0146 | 2023-03-20 |