Skip to content
Fencer Vulns
high 8.4

CVE-2026-100369 json

CliInvoke: Argument Injection in Extensibility Runner Factory

published 2026-09-25 44 d ago modified 2026-09-30 39 d ago also GHSA-j73w-8hfr-4gc9 , EUVD-2026-87354

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

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`.

Patch / fix

  • nuget CliInvoke 2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.2
  • nuget AlastairLundy.CliInvoke 2.0.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
41 d ago

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget CliInvoke
>=2.0.0, <2.8.5
>=2.9.0, <2.9.4
>=2.10.0, <2.10.5
>=3.0.0-alpha.1, <3.0.0-beta.2
2.8.5
2.9.4
2.10.5
3.0.0-beta.2
nuget AlastairLundy.CliInvoke
>=2.0.0-alpha.1, <2.0.2
2.0.2

Affected products

  • alastairlundy CliInvoke
  • alastairlundy AlastairLundy.CliInvoke

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.