
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 2.0.0, <= 2.8.4
Patched in 2.8.5
Vulnerable: >= 2.9.0, <= 2.9.3
Patched in 2.9.4
Vulnerable: >= 2.10.0, <= 2.10.4
Patched in 2.10.5
Vulnerable: >= 3.0.0-alpha.1, <= 3.0.0-beta.1
Patched in 3.0.0-beta.2
Vulnerable: >= 2.0.0-alpha.1, <= 2.0.0
Patched in 2.0.2
Details
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.
Upgrade to:
No complete workaround is available. Until you can upgrade:
" from any target or argument before passing it to the
factory. On shell runners, also strip ;, |, &, $, backtick,
and parentheses.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.
EPSS, exploit probability
Low0.36%
estimated chance of real-world exploitation in the next 30 days, higher than 29.9% of every CVE FIRST.org scores
Refreshed 11/9/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.