Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-100368 high CVSS 8.4

OS Command Injection in CliInvoke.Specializations (CVE-2026-100368)

Summary

OS command injection in CliInvoke.Specializations (CVE-2026-100368). Successful exploitation can lead to full system takeover. Exploitable via CliInvoke.Specializations. Mitigation: upgrade to 3.0.0-beta.1 or later.

Original description

The description as published by the source.

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 (;, |…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-100368 has been found in CliInvoke.Specializations.
Attackers can target a specific entry point like CliInvoke.Specializations over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade CliInvoke.Specializations to 3.0.0-beta.1 or later.
If unsure, ask your IT team or search "CliInvoke.Specializations CVE-2026-100368" on the vendor's site.

CVE-2026-100368 (CliInvoke.Specializations) — CWE-78 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Attack surface: CliInvoke.Specializations / PowershellProcessInvoker / CmdProcessInvoker / UsePowerShell
Patched: 3.0.0-beta.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in CliInvoke.Specializations. Attackers reach the vulnerable code path via CliInvoke.Specializations without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of CliInvoke.Specializations. Attack surface: CliInvoke.Specializations / PowershellProcessInvoker / CmdProcessInvoker / UsePowerShell.

🔥 Severity

Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.0.0-beta.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CliInvoke.Specializations' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'CliInvoke.Specializations' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で CliInvoke.Specializations を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade CliInvoke.Specializations to 3.0.0-beta.1

    ステージング環境で 3.0.0-beta.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

nuget CliInvoke.Specializations
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-beta.1"}]}]
nuget AlastairLundy.CliInvoke.Specializations
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details