How severe is CVE-2026-100368?

CVE-2026-100368 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-100368?

CVE-2026-100368 affects the following packages: CliInvoke.Specializations (NuGet), CliInvoke.Specializations (NuGet), CliInvoke.Specializations (NuGet), CliInvoke.Specializations (NuGet), CliInvoke.Specializations (NuGet), AlastairLundy.CliInvoke.Specializations (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2026-100368?

Update CliInvoke.Specializations to 2.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-100368 is resolved across your whole dependency graph.

How do I detect CVE-2026-100368 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CliInvoke.Specializations, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-100368 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-100368 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-100368 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-100368?

CVE-2026-100368 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-100368?

CVE-2026-100368 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-100368 published, and has it been updated?

CVE-2026-100368 was published on September 25, 2026 and was last updated on October 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

CVE-2026-100368 — CliInvoke.Specializations

HIGHFix: alastairlundy/CliInvoke@1e98582

CVE-2026-100368 is a high-severity (CVSS 8.4) OS Command Injection vulnerability in CliInvoke.Specializations. A fix is available for CliInvoke.Specializations — see the affected versions and patch details below.

CliInvoke.Specializations: Command injection in PowerShell and Cmd shell wrappers

Also known asGHSA-wrvw-254r-wpmv

Published

Sep 25, 2026

Updated

Oct 2, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-100368.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-100368 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

.NETCliInvoke.Specializations.NETCliInvoke.Specializations.NETCliInvoke.Specializations.NETCliInvoke.Specializations.NETCliInvoke.Specializations.NETAlastairLundy.CliInvoke.Specializations

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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 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)

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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CliInvoke.Specializations`	≥ 2.2.0&&< 2.8.5	2.8.5`dotnet add package CliInvoke.Specializations --version 2.8.5`
.NETNuGet	`CliInvoke.Specializations`	≥ 2.9.0&&< 2.9.4	2.9.4`dotnet add package CliInvoke.Specializations --version 2.9.4`
.NETNuGet	`CliInvoke.Specializations`	≥ 2.10.0&&< 2.10.5	2.10.5`dotnet add package CliInvoke.Specializations --version 2.10.5`
.NETNuGet	`CliInvoke.Specializations`	≥ 3.0.0-alpha.1&&< 3.0.0-beta.1	3.0.0-beta.1`dotnet add package CliInvoke.Specializations --version 3.0.0-beta.1`
.NETNuGet	`CliInvoke.Specializations`	≥ 3.0.0-alpha.8&&< 3.0.0-beta.1	3.0.0-beta.1`dotnet add package CliInvoke.Specializations --version 3.0.0-beta.1`
.NETNuGet	`AlastairLundy.CliInvoke.Specializations`	≥ 1.0.0-rc.1&&< 2.0.2	2.0.2`dotnet add package AlastairLundy.CliInvoke.Specializations --version 2.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CliInvoke.Specializations, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update CliInvoke.Specializations to 2.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-100368 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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 shel