CWE · MITRE source
CWE-826Premature Release of Resource During Expected Lifetime
The product releases a resource that is still intended to be used by itself or another actor.
This weakness focuses on errors in which the product should not release a resource, but performs the release anyway. This is different than a weakness in which the product releases a resource at the appropriate time, but it maintains a reference to the resource, which it later accesses. For this weakness, the resource should still be valid upon the subsequent access. When a product releases a resource that is still being used, it is possible that operations will still be taken on this resource, which may have been repurposed in the meantime, leading to issues similar to CWE-825. Consequences may include denial of service, information exposure, or code execution.
Last updated: 14 October 2026 20:41 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 (0)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 |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-32748 UPD | 6.7 | 7.5 | 0.0893 | 2026-03-26 |
CVE-2026-33526 UPD | 6.7 | 7.5 | 0.0894 | 2026-03-26 |
CVE-2026-49427 UPD | 6.6 | 8.8 | 0.0050 | 2026-08-19 |
CVE-2026-53322 UPD | 5.9 | 8.8 | 0.0013 | 2026-06-26 |
CVE-2026-31663 UPD | 5.6 | 7.8 | 0.0013 | 2026-04-24 |
CVE-2026-45984 UPD | 5.6 | 7.8 | 0.0018 | 2026-05-27 |
CVE-2024-51727 | 5.1 | 6.5 | 0.0053 | 2024-12-06 |
CVE-2023-1297 UPD | 4.1 | 4.9 | 0.0077 | 2023-06-02 |
CVE-2025-24912 UPD | 3.4 | 3.7 | 0.0077 | 2025-03-12 |
CVE-2024-58249 UPD | 3.3 | 3.7 | 0.0052 | 2025-04-16 |