Skip to content

← Actionable
High, CVSS 7.7amended

python-utcp: Full Process Environment Exposed to CLI Subprocess - Secrets Leakage via Command Injection

CVE-2026-45370GHSA-5v57-8rxj-3p2r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (utcp-cli 1.1.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI utcp-cli

    Affected
    <= 1.1.1
    Fixed in
    1.1.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-45370: 0.22% estimated exploitation activity in the next 30 days; percentile 13.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary prepareenvironment() in clicommunicationprotocol.py passes a full copy of os.environ to every CLI subprocess. When combined with the Command Injection vulnerability (CWE-78) in substituteutcpargs() tracked as GHSA-33p6-5jxp-p3x4, an attacker can exfiltrate all process-level secrets in a single tool call. Vulnerable Code Impact Any environment variable present in the host process is accessible to injected commands. In typical AI agent deployments this includes: - Cloud provider credentials (AWSSECRETACCESSKEY, AZURECLIENTSECRET) - Database connection strings (DATABASEURL) - LLM API keys (OPENAIAPIKEY, ANTHROPICAPIKEY) - Internal service tokens Proof of Concept Patched Fixed in utcp-cli 1.1.2. prepareenvironment no longer copies the full host environment. Inheritance is controlled by a new CliCallTemplate.inheritenvvars field: - null (default): a small built-in OS-specific allowlist (PATH, HOME, LANG on Unix; PATH, PATHEXT, SYSTEMROOT, USERPROFILE, etc. on Windows) is inherited…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5v57-8rxj-3p2r

  2. Revision 1 · created ·

    Published from osv record GHSA-5v57-8rxj-3p2r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45370

Advisory: python-utcp: Full Process Environment Exposed to CLI Subprocess - Secrets Leakage via Command Injection
IDs: CVE-2026-45370, GHSA-5v57-8rxj-3p2r
Record: https://patchnext.com/advisories/cve-2026-45370 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: utcp-cli 1.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI utcp-cli: affected <= 1.1.1; fixed in 1.1.2

## Suggested inspection (read-only)
- `python -m pip show utcp-cli`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on utcp-cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5v57-8rxj-3p2r (OSV record GHSA-5v57-8rxj-3p2r lists affected ranges: PyPI utcp-cli >=0 <1.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-5v57-8rxj-3p2r (GitHub-reviewed advisory GHSA-5v57-8rxj-3p2r lists affected ranges: PyPI utcp-cli >=0 <=1.1.1)

Commands are suggestions: review each one before running it.

Loading voting…