← Back
CVE-2026-45369
high
CVSS 8.3
OS Command Injection in utcp-cli (CVE-2026-45369)
Summary
OS command injection in utcp-cli (CVE-2026-45369). Successful exploitation can lead to full system takeover. Exploitable via ``_substitute_utcp_args``. Mitigation: upgrade to `1.1.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45369** has been found in utcp-cli.
Attackers can target a specific entry point like ``_substitute_utcp_args`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.3/10.
What to do: upgrade utcp-cli to **1.1.2** or later.
If unsure, ask your IT team or search "utcp-cli CVE-2026-45369" on the vendor's site.
CVE-2026-45369 (utcp-cli) — CWE-78 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `_substitute_utcp_args` / `cli_communication_protocol.py` / `tool_args` / `shlex.quote`
Patched: `1.1.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.
❓ What is the problem
**OS command injection** (CWE-78) exists in utcp-cli. Attackers reach the vulnerable code path via ``_substitute_utcp_args`` without authentication.
📍 Affected scope
utcp-cli — . Attack surface: `_substitute_utcp_args` / `cli_communication_protocol.py` / `tool_args` / `shlex.quote`.
🔥 Severity
Severity: High (CVSS 8.3/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.1.2**.
🛡️ 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 'utcp-cli' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'utcp-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `utcp-cli` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade utcp-cli to 1.1.2ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
utcp-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
PyPI
utcp-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]