CWE-14Compiler Removal of Code to Clear Buffers

Abstraction: Variant · CVEs in our corpus: 10

Sensitive memory is cleared according to the source code, but compiler optimizations leave the memory untouched when it is not read from again, aka "dead store removal."

This compiler optimization error occurs when:

Last updated: 14 October 2026 20:41 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent

Stop it (NIST 800-53 / CSF Protect)

PR.DS-10
PR.PS-06
SA-8 Security and Privacy Engineering Principles
SA-11 Developer Testing and Evaluation

Detect

Catch it (CSF Detect / Respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

—

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-2025-64646`	4.7	6.2	0.0017	2026-03-25
`CVE-2023-1132`	4.3	5.3	0.0048	2023-05-18
`CVE-2023-2481`	4.3	5.3	0.0048	2023-05-18
`CVE-2023-32098`	4.3	5.3	0.0053	2023-05-18
`CVE-2023-32099`	4.3	5.3	0.0053	2023-05-18
`CVE-2023-32100`	4.3	5.3	0.0048	2023-05-18
`CVE-2026-48984`	3.6	4.7	0.0015	2026-06-18
`CVE-2023-0965`	2.9	3.1	0.0048	2023-05-18
`CVE-2023-32096`	2.9	3.1	0.0048	2023-05-18
`CVE-2023-32097`	2.9	3.1	0.0048	2023-05-18