CWE-146Improper Neutralization of Expression/Command Delimiters

Abstraction: Variant · CVEs in our corpus: 10

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as expression or command delimiters when they are sent to a downstream component.

As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.

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.PS-06
SI-10 Information Input Validation

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-2024-20329`	7.2	9.9	0.0115	2024-10-23
`CVE-2023-20128`	7.0	7.2	0.3039	2023-04-05
`CVE-2023-20117`	7.0	7.2	0.3039	2023-04-05
`CVE-2025-53192`	6.6	8.8	0.0056	2025-08-18
`CVE-2023-20035`	5.7	7.8	0.0022	2023-03-23
`CVE-2022-4055`	5.5	7.4	0.0068	2022-11-19
`CVE-2024-20470`	5.5	7.2	0.0062	2024-10-02
`CVE-2026-20288`	5.1	6.5	0.0064	2026-08-05
`CVE-2025-20237`	4.5	6.0	0.0015	2025-08-14
`CVE-2026-22266`	3.8	4.7	0.0029	2026-02-19