cve.bz

CVE-2026-100368 alastairlundy cliinvoke.specializations: OS Command Injection

8.4 highEPSS 0.6%Fix available

High (8.4) in alastairlundy cliinvoke.specializations. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in CliInvoke.Specializations 2.10.5, 2.8.5, 2.9.4.

On this page
CliInvoke is a .NET library for invoking command-line programs, and its `CliInvoke.Specializations` packages provide specialized wrappers for shells such as PowerShell and Windows Command Prompt. `CliInvoke.Specializations` versions 2.2.0 through 2.8.4, 2.9.0 through 2.9.3, 2.10.0 through 2.10.4, 3.0.0-alpha.1 through 3.0.0-alpha.4, and 3.0.0-alpha.8 through 3.0.0-alpha.10, as well as `AlastairLundy.CliInvoke.Specializations` versions 1.0.0-rc.1 through 1.6.1.1, contain an OS command injection vulnerability in their PowerShell and Cmd wrappers. The wrappers pass a caller-controlled target and arguments to `pwsh -Command` or `cmd /c` using a single `ProcessStartInfo.Arguments` string, allowing a double quote in untrusted input to break operating-system-level quoting and cause the shell to execute an additional command with the host process's privileges. The vulnerability is patched in `CliInvoke.Specializations` versions 2.8.5, 2.9.4, 2.10.5, and 3.0.0-beta.1, and in `AlastairLundy.CliInvoke.Specializations` version 2.0.2. No complete workaround is available; users unable to upgrade should reject or remove double quotes from target paths and arguments, additionally reject shell metacharacters in versions 2.2.0 through 2.9.2 and 3.0.0-alpha.1 through 3.0.0-alpha.4, or bypass the PowerShell and Cmd wrappers and invoke target processes directly when handling untrusted input.

Severity

CVSS 3.1

8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • CliInvoke.Specializations (NuGet): fixed in 2.8.5, 2.9.4, 2.10.5, 3.0.0-beta.1
  • AlastairLundy.CliInvoke.Specializations (NuGet): fixed in 2.0.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-100368 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-100368?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-100368?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-100368 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
alastairlundy CliInvoke.Specializations>= 2.2.0, <= 2.8.4
alastairlundy CliInvoke.Specializations>= 2.9.0, <= 2.9.3
alastairlundy CliInvoke.Specializations>= 2.10.0, <= 2.10.4
alastairlundy CliInvoke.Specializations>= 3.0.0-alpha.1, <= 3.0.0-alpha.4
alastairlundy CliInvoke.Specializations>= 3.0.0-alpha.8, <= 3.0.0-alpha.10
alastairlundy CliInvoke.Specializations>= 1.0.0-rc.1, <= 1.6.1.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wrvw-254r-wpmvNuGetCliInvoke.Specializations>=2.2.0 <2.8.52.8.5
GHSA-wrvw-254r-wpmvNuGetCliInvoke.Specializations>=2.9.0 <2.9.42.9.4
GHSA-wrvw-254r-wpmvNuGetCliInvoke.Specializations>=2.10.0 <2.10.52.10.5
GHSA-wrvw-254r-wpmvNuGetCliInvoke.Specializations>=3.0.0-alpha.1 <3.0.0-beta.13.0.0-beta.1
GHSA-wrvw-254r-wpmvNuGetCliInvoke.Specializations>=3.0.0-alpha.8 <3.0.0-beta.13.0.0-beta.1
GHSA-wrvw-254r-wpmvNuGetAlastairLundy.CliInvoke.Specializations>=1.0.0-rc.1 <2.0.22.0.2

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON