CliInvoke.Specializations has command injection in PowerShell and Cmd shell wrappers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-100368: 0.58% estimated exploitation activity in the next 30 days; percentile 47.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Patches The Specializations Packages now deliver the command via ProcessStartInfo.ArgumentList (natively where supported, and polyfilled in older TFMs), so that…

Published by the source

25 Sep 2026, 21:41 UTC

Last modified by the source

25 Sep 2026, 23:00 UTC

Source last checked

26 Oct 2026, 17:05 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wrvw-254r-wpmv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wrvw-254r-wpmv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-100368

Advisory: CliInvoke.Specializations has command injection in PowerShell and Cmd shell wrappers
IDs: CVE-2026-100368, GHSA-wrvw-254r-wpmv
Record: https://patchnext.com/advisories/cve-2026-100368 (revision 2, source checked 26 Oct 2026, 17:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: alastairlundy.cliinvoke.specializations 2.0.2; cliinvoke.specializations 3.0.0-beta.1, 2.10.5, 2.9.4, 2.8.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet alastairlundy.cliinvoke.specializations: affected >= 1.0.0-rc.1, <= 1.6.1.1; fixed in 2.0.2
- NuGet cliinvoke.specializations: affected >= 2.2.0, <= 2.8.4; >= 2.9.0, <= 2.9.3; >= 2.10.0, <= 2.10.4; >= 3.0.0-alpha.1, <= 3.0.0-alpha.4; >= 3.0.0-alpha.8, <= 3.0.0-alpha.10; fixed in 2.9.4, 2.10.5, 3.0.0-beta.1, 2.8.5

## Suggested inspection (read-only)
- NuGet alastairlundy.cliinvoke.specializations: check the installed version with your package manager.
- NuGet cliinvoke.specializations: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on alastairlundy.cliinvoke.specializations, cliinvoke.specializations.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wrvw-254r-wpmv (OSV record GHSA-wrvw-254r-wpmv lists affected ranges: NuGet cliinvoke.specializations >=2.2.0 =2.9.0 =2.10.0 =3.0.0-alpha.1 =3.0.0-alpha.8 =1.0.0-rc.1 <2.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-wrvw-254r-wpmv (GitHub-reviewed advisory GHSA-wrvw-254r-wpmv lists affected ranges: NuGet cliinvoke.specializations >=2.2.0 =2.9.0 =2.10.0 =3.0.0-alpha.1 =3.0.0-alpha.8 =1.0.0-rc.1 <=1.6.1.1)

Commands are suggestions: review each one before running it.