Loading...
Skip to main content

CVE-2026-100369 — CliInvoke: Argument Injection in CliInvoke — CVE...

HIGH

CliInvoke: Argument Injection in Extensibility Runner Factory

Published September 25, 2026Updated September 25, 2026Source: osv

Summary

### Impact An argument-injection vulnerability exists in the `CliInvoke` package's runner factory: `RunnerProcessFactory` on the 2.x line and `RunnerConfigurationFactory` on the 3.x line. The factory joins the runner arguments, the caller's target, and the caller's arguments into a single `ProcessStartInfo.Arguments` string and hands it to the OS. The OS command-line parser re-tokenizes the string before the runner sees it. A double quote (`"`) in the target or in any argument closes the OS-level quoted region and lets the next character enter argv as a separate element. ### Patches Upgrade to: - **2.8.5** (2.8.x line) - **2.9.4** (2.9.x line) - **2.10.5** (2.10.x line) - **3.0.0-beta.2** (3.x pre-release line) ### Workarounds No complete workaround is available. Until you can upgrade: - Strip `"` from any target or argument before passing it to the factory. On shell runners, also strip `;`, `|`, `&`, `$`, backtick, and parentheses. - Or bypass the factory entirely and build the `ProcessConfiguration` directly. Set `ArgumentList` explicitly to the argv you want the runner to receive. These are partial mitigations. They shift the quoting problem to your code.

Advisory Timeline

  • First published September 25, 2026 (16 days ago).
  • Last revised September 25, 2026 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update CliInvoke to 3.0.0-beta.2 or later
dotnet add package CliInvoke --version 3.0.0-beta.2
NuGet
Update CliInvoke to 2.8.5 or later
dotnet add package CliInvoke --version 2.8.5
NuGet
Update CliInvoke to 2.9.4 or later
dotnet add package CliInvoke --version 2.9.4
NuGet
Update AlastairLundy.CliInvoke to 2.0.2 or later
dotnet add package AlastairLundy.CliInvoke --version 2.0.2
NuGet
Update CliInvoke to 2.10.5 or later
dotnet add package CliInvoke --version 2.10.5

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (5)

Affects 1 ecosystem: nuget (2).

PackageEcosystemAffectedFixed In
CliInvoke
nuget
All versions3.0.0-beta.2
CliInvoke
nuget
2.0.0, 2.0.1, 2.1.0, 2.1.1 (+32 more)2.8.5
CliInvoke
nuget
2.9.0, 2.9.1, 2.9.2, 2.9.32.9.4
AlastairLundy.CliInvoke
nuget
2.0.02.0.2
CliInvoke
nuget
2.10.1, 2.10.2, 2.10.3, 2.10.42.10.5

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.4 score means for each attack dimension.

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-100369?
CliInvoke: Argument Injection in Extensibility Runner Factory This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.4/10).
How do I check if my project is affected by CVE-2026-100369?
CVE-2026-100369 affects CliInvoke and AlastairLundy.CliInvoke. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-100369 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.4

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-j73w-8hfr-4gc9

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies