BaseDraft

CWE-460Improper Cleanup on Thrown Exception

Category: other

Description

The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. Often, when functions or loops become complicated, some level of resource cleanup is needed throughout execution. Exceptions can disturb the flow of the code and prevent the necessary cleanup from happening.

Common consequences· 1

  • Other — Varies by Context
    The code could be left in a bad state.

Potential mitigations· 1

  • [Implementation]If one breaks from a loop or function by throwing an exception, make sure that cleanup happens or that you should exit the program. Use throwing exceptions sparsely.

References

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

(incoming)1

TypeTargetConfidenceTier
VulnerabilityCVE-2026-40583cve-2026-405830%live

Related by meaning· 6

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

CWE
Incomplete Cleanup
CWE
Incorrect Control Flow Scoping
CWE
Improper Resource Shutdown or Release
CWE
Missing Standardized Error Handling Mechanism
CWE
Improper Handling of Exceptional Conditions
CWE
Missing Reference to Active Allocated Resource
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.