CWE · MITRE source
CWE-404Improper Resource Shutdown or Release
The product does not release or incorrectly releases a resource before it is made available for re-use.
When a resource is created or allocated, the developer is responsible for properly releasing the resource as well as accounting for all potential paths of expiration or invalidation, such as a set period of time or revocation.
Last updated: 15 October 2026 07:26 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (4)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-10 | Network Disconnect | SC | Mandates explicit shutdown of the network connection at session conclusion, directly addressing improper resource release. |
SC-4 | Information in Shared System Resources | SC | Requires proper shutdown/release procedures that include overwriting or isolating data to block unintended transfer via reused system objects. |
CP-5 | Contingency Plan Update | CP | Contingency plan updates incorporate proper resource shutdown and release steps, preventing attackers from leveraging incomplete cleanup during recovery scenarios. |
SI-17 | Fail-safe Procedures | SI | Procedures can mandate orderly shutdown or release of resources when failures occur, preventing improper resource handling after a fault. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2017-6627 KEV UPD | 8.5 | 7.5 | 0.0616 | 2017-09-07 |
CVE-2018-8405 KEV UPD | 8.5 | 7.8 | 0.0344 | 2018-08-15 |
CVE-2018-8406 KEV UPD | 8.5 | 7.8 | 0.0344 | 2018-08-15 |
CVE-2018-8611 KEV UPD | 8.5 | 7.8 | 0.0420 | 2018-12-12 |
CVE-2018-8639 KEV UPD | 8.5 | 7.8 | 0.2218 | 2018-12-12 |
CVE-2018-8120 KEV UPD | 7.9 | 7.0 | 0.7343 | 2018-05-09 |
CVE-2018-8450 UPD | 7.7 | 8.8 | 0.1608 | 2018-11-14 |
CVE-2022-44267 UPD | 7.7 | 6.5 | 0.7658 | 2023-02-06 |
CVE-2023-24444 UPD | 7.5 | 9.8 | 0.0115 | 2023-01-26 |
CVE-2022-25762 UPD | 7.4 | 8.6 | 0.0840 | 2022-05-13 |
CVE-2018-8210 UPD | 7.3 | 7.8 | 0.2524 | 2018-06-14 |
CVE-2026-41869 | 7.0 | 9.1 | 0.0072 | 2026-09-09 |
CVE-2024-31611 UPD | 6.9 | 9.1 | 0.0057 | 2024-06-10 |
CVE-2017-5650 UPD | 6.7 | 7.5 | 0.0828 | 2017-04-17 |
CVE-2018-8213 UPD | 6.7 | 7.8 | 0.0861 | 2018-06-14 |
CVE-2022-2591 UPD | 6.7 | 7.5 | 0.0890 | 2022-08-01 |
CVE-2025-8761 UPD | 6.7 | 7.5 | 0.0858 | 2025-08-13 |
CVE-2017-1145 UPD | 6.6 | 8.6 | 0.0191 | 2017-03-20 |
CVE-2019-1708 UPD | 6.6 | 8.6 | 0.0206 | 2019-05-03 |
CVE-2020-26070 UPD | 6.6 | 8.6 | 0.0190 | 2020-11-12 |
CVE-2018-19591 UPD | 6.5 | 7.5 | 0.0553 | 2018-12-04 |
CVE-2018-8410 UPD | 6.4 | 7.8 | 0.0398 | 2018-09-13 |
CVE-2019-1706 UPD | 6.4 | 8.6 | 0.0107 | 2019-05-03 |
CVE-2025-48989 UPD | 6.4 | 7.5 | 0.0369 | 2025-08-13 |
CVE-2025-8671 UPD | 6.4 | 7.5 | 0.0362 | 2025-08-13 |