Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100369 Overview
CVE-2026-100369 is an argument-injection vulnerability in CliInvoke, a .NET library for invoking command-line programs and wrapping executable processes. The flaw affects CliInvoke versions 2.0.0 through 3.0.0-beta.1 and the formerly named AlastairLundy.CliInvoke package versions 2.0.0-alpha.1 through 2.0.0. The RunnerProcessFactory (2.x line) and RunnerConfigurationFactory (3.x line) concatenate caller-controlled input into a single ProcessStartInfo.Arguments string. An attacker who controls a target or argument value can inject a double quote to break out of the quoted region and append unintended arguments. When paired with a shell runner, this can lead to arbitrary command execution.
Critical Impact
Argument injection in shell runner contexts enables arbitrary command execution with the privileges of the invoking .NET process.
Affected Products
- CliInvoke 2.0.0 through 2.8.4, 2.9.0 through 2.9.3, 2.10.0 through 2.10.4
- CliInvoke 3.0.0-alpha.1 through 3.0.0-beta.1
- AlastairLundy.CliInvoke 2.0.0-alpha.1 through 2.0.0
Discovery Timeline
- 2026-09-25 - CVE-2026-100369 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-100369
Vulnerability Analysis
The vulnerability is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command. CliInvoke's factory classes build a single argument string that is later parsed by the operating system's command-line tokenizer. Because the factory concatenates runner arguments, the target executable path, and caller-supplied arguments without escaping embedded quote characters, a malicious value can terminate the quoted region and inject additional tokens into the resulting argument vector.
When the factory is used with a shell runner such as cmd.exe, /bin/sh, or pwsh, injected tokens are interpreted as shell metacharacters or additional commands. This elevates argument injection to arbitrary command execution within the shell context.
Root Cause
The root cause is unsafe string concatenation inside RunnerProcessFactory on the 2.x branch and RunnerConfigurationFactory on the 3.x branch. Both factories flatten structured input into ProcessStartInfo.Arguments rather than using the safer ArgumentList collection, which handles OS-level quoting correctly. Double quotes in a target or argument value are passed through verbatim and alter the parsed token boundaries.
Attack Vector
Exploitation requires local access and the ability to influence target or argument values passed to a vulnerable factory. An attacker supplies input containing a double quote followed by crafted content. The OS argument parser treats the injected tokens as separate arguments, which the shell runner then interprets as commands. Refer to the GitHub Security Advisory GHSA-j73w-8hfr-4gc9 for the full technical description.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-100369
Indicators of Compromise
- Unexpected child processes spawned from .NET applications that depend on CliInvoke or AlastairLundy.CliInvoke.
- Process command lines containing stray double-quote characters or shell metacharacters such as &, |, ;, or backticks in argument positions.
- Shell runner invocations (cmd.exe, sh, bash, pwsh) originating from application processes that normally invoke only specific executables.
Detection Strategies
- Audit source code and dependency manifests (*.csproj, packages.lock.json) for vulnerable CliInvoke or AlastairLundy.CliInvoke versions.
- Instrument process-creation telemetry to flag command lines where a quoted argument region is followed by additional unexpected tokens.
- Review application logs for input values containing " characters immediately followed by whitespace and additional parameters.
Monitoring Recommendations
- Enable endpoint process-creation logging and forward events to a centralized data lake for correlation across hosts.
- Baseline the expected child-process tree for each service that uses CliInvoke and alert on deviations.
- Monitor for shell runner invocations correlated with external or user-supplied input reaching the application.
How to Mitigate CVE-2026-100369
Immediate Actions Required
- Upgrade CliInvoke to version 2.8.5, 2.9.4, 2.10.5, or 3.0.0-beta.2 depending on the branch in use.
- Upgrade AlastairLundy.CliInvoke to version 2.0.2.
- Inventory all .NET services that reference either package and prioritize those that invoke shell runners or process untrusted input.
Patch Information
The maintainers published fixes in CliInvoke versions 2.8.5, 2.9.4, 2.10.5, and 3.0.0-beta.2, and in AlastairLundy.CliInvoke version 2.0.2. Patch details are documented in the GitHub Security Advisory GHSA-j73w-8hfr-4gc9.
Workarounds
- No complete workaround exists. Partial mitigation requires stripping double quotes from all target and argument values before passing them to the factory.
- When using shell runners, additionally strip shell metacharacters such as &, |, ;, `, $, (, and ) from caller-controlled values.
- Bypass the vulnerable factory by constructing a ProcessConfiguration directly with an explicit ArgumentList, which delegates OS-level quoting to the runtime.
# Update vulnerable packages via the .NET CLI
dotnet add package CliInvoke --version 2.10.5
dotnet add package AlastairLundy.CliInvoke --version 2.0.2
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

