Threadlinqs IntelligenceStart free

Weakness · BaseCWE-617

CWE-617: Reachable Assertion

KEV-linkedBase

As of 2026-11-19, CWE-617 (Reachable Assertion) underlies 21 CVEs tracked by Threadlinqs, 1 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 4 tracked threats.

CVEs
21Mapped to CWE-617
CISA KEV
1Exploited in the wild
Critical
0CVSS v3 critical CVEs
Threats
4Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-617?

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.

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

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

Consequences

  • Availability — DoS: Crash, Exit, or Restart. An attacker that can trigger an assert statement can still lead to a denial of service if the relevant code can be triggered by an attacker, and if the scope of the assert() extends beyond the attacker's own session.

Source: MITRE CWE, common consequences.

How CWE-617 is exploited in the wild

Threadlinqs maps 21 CVEs to CWE-617, published between 2015-07-29 and 2026-11-11. 1 is listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild. By CVSS v3 severity the set splits into 10 high, 8 medium, 2 low. The highest EPSS score in the set is 91.8% (CVE-2015-5477), the modelled probability of exploitation in the next 30 days. 4 tracked threats reference CWE-617 directly or through a CVE it covers; the most recent is “Node.js November 2026 Security Releases Patch 16 Vulnerabilities (HTTP/2 crashes, HTTPS heap/TLS key leak CVE-2026-123864, TLS client-certificate auth bypass)” (2026-11-12). Affected products concentrate in The Libreswan Project (3), vllm-project (3), IBM (2), among 10 vendors in total.

Vulnerabilities (CVEs)

All 21 CVEs mapped to CWE-617, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

4 tracked threats cite CWE-617:

Mitigations

  • Implementation: Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
  • Implementation / Input Validation: Perform input validation on user data.

Source: MITRE CWE, potential mitigations.

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.