Cyber Resilience

CWE · MITRE source

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

Abstraction: Base · CVEs in our corpus: 415

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

When creating commands using interpolation into a string, developers may assume that only the arguments/options that they specify will be processed. This assumption may be even stronger when the programmer has encoded the command in a way that prevents separate commands from being provided maliciously, e.g. in the case of shell metacharacters. When constructing the command, the developer may use whitespace or other delimiters that are required to separate arguments when the command. However, if an attacker can provide an untrusted input that contains argument-separating delimiters, then the resulting command will have more arguments than intended by the developer. The attacker may then be able to change the behavior of the command. Depending on the functionality supported by the extraneous arguments, this may have security-relevant consequences.

Last updated: 22 August 2026 20:22 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: partial · 2 mapping(s) from 1 framework(s): CAPEC 2 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A05:2025 Injection.

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
  • SA-11 Developer Testing and Evaluation
  • SI-10 Information Input Validation
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5

NIST 800-53 r5 controls that address this weakness (0)AI-assisted

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-2016-10033 KEV 9.99.80.99712016-12-30
CVE-2018-17456 9.99.80.97362018-10-06
CVE-2026-24061 KEV 9.99.80.97882026-01-21
CVE-2021-33564 9.89.80.72142021-05-29
CVE-2022-23221 9.79.80.64772022-01-19
CVE-2022-36804 KEV 9.28.80.99082022-08-25
CVE-2020-21224 9.19.80.38752021-02-22
CVE-2024-24576 8.610.00.20342024-04-09
CVE-2018-19518 8.37.50.95232018-11-25
CVE-2019-6453 8.38.10.54292019-02-18
CVE-2007-0882 8.20.00.97852007-02-12
CVE-2021-3401 8.29.80.10482021-02-04
CVE-2021-26937 8.29.80.09152021-02-09
CVE-2022-25766 8.28.80.33892022-03-21
CVE-2021-1531 8.18.80.30492021-05-22
CVE-2024-41710 KEV 8.17.20.41652024-08-12
CVE-2020-13699 8.08.80.25792020-07-29
CVE-2019-3463 7.99.80.04872019-02-06
CVE-2020-15692 7.99.80.04202020-08-14
CVE-2022-24437 7.99.80.03982022-05-01
CVE-2019-10746 7.89.80.03512019-08-23
CVE-2019-12148 7.89.80.03532019-10-22
CVE-2020-5599 7.89.80.03492020-07-07
CVE-2020-5648 7.89.80.03472020-11-06
CVE-2021-31909 7.89.80.03212021-05-11