CWE-141Improper Neutralization of Parameter/Argument Delimiters

Abstraction: Variant · CVEs in our corpus: 12

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as parameter or argument 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-2022-29873`	7.7	9.8	0.0199	2022-05-20
`CVE-2022-41665`	7.6	9.8	0.0141	2022-10-11
`CVE-2023-28815`	7.6	9.8	0.0142	2025-10-17
`CVE-2020-7868`	7.2	9.6	0.0270	2021-06-29
`CVE-2022-29872`	6.8	8.8	0.0150	2022-05-20
`CVE-2024-0840`	6.7	8.8	0.0088	2024-04-29
`CVE-2026-20200`	6.7	8.8	0.0073	2026-08-05
`CVE-2026-19594`	6.1	8.1	0.0050	2026-08-12
`CVE-2025-31329`	4.6	6.2	0.0036	2025-05-13
`CVE-2025-20338`	4.5	6.0	0.0016	2025-09-24
`CVE-2026-66323`	4.4	5.4	0.0041	2026-08-28