Threadlinqs IntelligenceStart free

Weakness · BaseCWE-459

CWE-459: Incomplete Cleanup

Base

As of 2026-11-19, CWE-459 (Incomplete Cleanup) underlies 13 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 8 tracked threats.

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

Last updated:

What is CWE-459?

The product does not properly "clean up" and remove temporary or supporting resources after they have been used.

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

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

Consequences

  • Other, Confidentiality, Integrity — Other, Read Application Data, Modify Application Data, DoS: Resource Consumption (Other). It is possible to overflow the number of temporary files because directories typically have limits on the number of files allowed. This could create a denial of service problem.

Source: MITRE CWE, common consequences.

How CWE-459 is exploited in the wild

Threadlinqs maps 13 CVEs to CWE-459, published between 2025-06-10 and 2026-11-11. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 2 critical, 2 high, 3 medium, 5 low. The highest EPSS score in the set is 0.6% (CVE-2026-34263), the modelled probability of exploitation in the next 30 days. 8 tracked threats reference CWE-459 directly or through a CVE it covers; the most recent is “Google Chrome 157 Stable Update Fixes 83 Security Flaws Including 5 Critical Use-After-Free Bugs (CVE-2026-126885, CVE-2026-126895, CVE-2026-126879, CVE-2026-126846, CVE-2026-126911)” (2026-11-12). Affected products concentrate in Google (4), Arista Networks (3), zephyrproject (2), among 7 vendors in total.

Vulnerabilities (CVEs)

All 13 CVEs mapped to CWE-459, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

8 tracked threats cite CWE-459:

Mitigations

  • Architecture and Design, Implementation: Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.

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.