Threadlinqs IntelligenceStart free

Weakness · BaseCWE-835

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

Base

As of 2026-10-05, CWE-835 (Infinite Loop) underlies 4 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 2 tracked threats.

CVEs
4Mapped to CWE-835
CISA KEV
0None listed yet
Critical
0CVSS v3 critical CVEs
Threats
2Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-835?

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

CWE-835 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Not Language-Specific; Not Technology-Specific.

Source: MITRE CWE (CWE-835 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Availability — DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification. An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.

Source: MITRE CWE, common consequences.

How CWE-835 is exploited in the wild

Threadlinqs maps 4 CVEs to CWE-835, published between 2026-06-18 and 2026-09-09. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 4 medium. The highest EPSS score in the set is 0.3% (CVE-2026-88002), the modelled probability of exploitation in the next 30 days. 2 tracked threats reference CWE-835 directly or through a CVE it covers; the most recent is “Public PoC Released for Critical libssh2 Client-Side SSH Flaw (CVE-2026-55200)” (2026-07-11). Affected products concentrate in open-webui (2), The Tcpdump Group (1), mcdope (1).

Vulnerabilities (CVEs)

All 4 CVEs mapped to CWE-835, CISA KEV first, then by CVSS score.

Affected vendors

  • open-webui — 2 CVEs
  • The Tcpdump Group — 1 CVE
  • mcdope — 1 CVE

Threat activity

2 tracked threats cite CWE-835:

Detection methods (MITRE CWE)

  • Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.