BaseDraft

CWE-459Incomplete Cleanup

Category: other

Description

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

Common consequences· 1

  • 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.

Potential mitigations· 1

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

References

  1. https://cwe.mitre.org/data/definitions/459.html

(incoming)6

TypeTargetConfidenceTier
VulnerabilityCVE-2025-21609cve-2025-216090%live
VulnerabilityCVE-2025-43711cve-2025-437110%live
VulnerabilityCVE-2025-66467cve-2025-664670%live
VulnerabilityCVE-2025-66675cve-2025-666750%live
VulnerabilityCVE-2026-28268cve-2026-282680%live
VulnerabilityCVE-2026-34263cve-2026-342630%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Cleanup on Thrown Exception
CWE
Missing Release of Resource after Effective Lifetime
CWE
Missing Release of Memory after Effective Lifetime
CWE
Improper Resource Shutdown or Release
CWE
Missing Reference to Active Allocated Resource
CWE
Improper Control of a Resource Through its Lifetime
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.