Summary
CliInvoke.Specializations has command injection in PowerShell and Cmd shell wrappers
Workarounds
No complete workaround is available. Until upgraded:
- Reject or strip
"from any target path or argument passed to the PowerShell/Cmd wrappers. On 2.2.0 – 2.9.2 and 3.0.0-alpha.1 – alpha.4, also reject shell metacharacters (;,|,&,$, backtick, parentheses). - Alternatively, bypass the wrappers for untrusted input and invoke the target process directly so that no second shell parse of the data occurs.
Impact
An OS command injection vulnerability exists in the PowerShell and Cmd shell wrappers provided by the CliInvoke.Specializations package (the PowershellProcessInvoker/CmdProcessInvoker invokers, and the UsePowerShell/UseCmd middleware in v3 pre-release versions).
The wrappers re-run a caller-supplied target and arguments inside a shell command (pwsh -Command ... / cmd /c ...). In affected versions the wrapped command was delivered to the operating system as a single ProcessStartInfo.Arguments string. The OS command-line parser re-tokenizes that string before the shell parses it, so a double quote (") in the target or arguments breaks OS-level quoting and lets the wrapped shell reassemble a second, unintended command.
An attacker could exploit this to execute arbitrary commands with the privileges of the host process.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2026-100368 has a CVSS score of 8.4 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.1, 2.0.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The Specializations Packages now deliver the command via ProcessStartInfo.ArgumentList (natively where supported, and polyfilled in older TFMs), so that the operating system passes argv verbatim and only the shell parses the command once.
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.1 (3.x pre-release line)
Frequently Asked Questions
- What is CVE-2026-100368? CVE-2026-100368 is a high-severity OS command injection vulnerability in CliInvoke.Specializations (nuget), affecting versions >= 2.2.0, <= 2.8.4. It is fixed in 2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.1, 2.0.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2026-100368? CVE-2026-100368 has a CVSS score of 8.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-100368?
CliInvoke.Specializations(nuget) (versions >= 2.2.0, <= 2.8.4)AlastairLundy.CliInvoke.Specializations(nuget) (versions >= 1.0.0-rc.1, <= 1.6.1.1)
- Is there a fix for CVE-2026-100368? Yes. CVE-2026-100368 is fixed in 2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.1, 2.0.2. Upgrade to this version or later.
- Is CVE-2026-100368 exploitable, and should I be worried? Whether CVE-2026-100368 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-100368 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-100368?
- Upgrade
CliInvoke.Specializationsto 2.8.5 or later - Upgrade
CliInvoke.Specializationsto 2.9.4 or later - Upgrade
CliInvoke.Specializationsto 2.10.5 or later - Upgrade
CliInvoke.Specializationsto 3.0.0-beta.1 or later - Upgrade
CliInvoke.Specializationsto 3.0.0-beta.1 or later - Upgrade
AlastairLundy.CliInvoke.Specializationsto 2.0.2 or later
- Upgrade