Vulnerability in CliInvoke (CVE-2026-100369)
Summary
Vulnerability in CliInvoke (CVE-2026-100369). Successful exploitation can lead to full system takeover. Exploitable via CliInvoke. Mitigation: upgrade to 3.0.0-beta.2 or later.
Original description
The description as published by the source.
Impact
An argument-injection vulnerability exists in the CliInvoke
package's runner factory: RunnerProcessFactory on the 2.x line and
RunnerConfigurationFactory on the 3.x line.
The factory joins the runner arguments, the caller's target, and the
caller's arguments into a single ProcessStartInfo.Arguments string and
hands it to the OS. The OS command-line parser re-tokenizes the string
before the runner sees it. A double quote (") in the target or in any
argument closes the OS-level quoted region and lets the next character
enter argv as a separate element.
Patches
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.2 (3.x pre-release line)
Workarounds
No complete workaround is available. Until you can upgrade:
- Strip
"from any target or argument before passing it to the
factory. On shell runners, also strip;,|,&,$, backtick,
and parentheses. - Or bypass the factory entirely and build the
ProcessConfiguration
directly. SetArgumentListexplicitly to the argv you want the
runner to receive.
These are partial mitigations. They shift the quoting problem to your
code.
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-100369 has been found in CliInvoke.
Attackers can target a specific entry point like CliInvoke 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 to 3.0.0-beta.2 or later.
If unsure, ask your IT team or search "CliInvoke CVE-2026-100369" on the vendor's site.
CVE-2026-100369 (CliInvoke) — CWE-88 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Attack surface: CliInvoke / RunnerProcessFactory / RunnerConfigurationFactory / ProcessStartInfo.Arguments
Patched: 3.0.0-beta.2 — 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.
A vulnerability (CWE-88) exists in CliInvoke. Attackers reach the vulnerable code path via CliInvoke without authentication.
Check the vendor advisory for the affected versions of CliInvoke. Attack surface: CliInvoke / RunnerProcessFactory / RunnerConfigurationFactory / ProcessStartInfo.Arguments.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to 3.0.0-beta.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'CliInvoke' . 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
-
1Identify exposure identify
grep -r 'CliInvoke' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
CliInvokeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade CliInvoke to 3.0.0-beta.2ステージング環境で 3.0.0-beta.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com