CVE-2026-45369
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpython-utcp is the python implementation of UTCP. Prior to 1.1.3, the _substitute_utcp_args method in cli_communication_protocol.py inserts user-controlled tool_args values directly into shell command strings without any sanitization or escaping. These commands are then executed via /bin/bash -c (Unix) or powershell.exe -Command (Windows), allowing an attacker to inject arbitrary shell commands. This vulnerability is fixed in 1.1.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepython-utcp versions before 1.1.3 contain a command injection vulnerability in the _substitute_utcp_args method within cli_communication_protocol.py. User-supplied tool_args values are concatenated directly into shell command strings without sanitization or escaping, then executed through /bin/bash -c on Unix or powershell.exe -Command on Windows, allowing arbitrary command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed python-utcp versionRun 'pip show python-utcp' or 'pip list | grep utcp' to see the installed version numberAffected if The installed version is below 1.1.3
-
Locate cli_communication_protocol.pyFind the file in your python environment (e.g., run 'python -c "import utcp; print(utcp.__file__)"' then navigate to cli_communication_protocol.py in the same directory)Affected if The file exists in the environment
-
Inspect _substitute_utcp_args method for vulnerable code patternOpen cli_communication_protocol.py and locate the _substitute_utcp_args method. Look for direct string concatenation of tool_args into command strings without shlex.quote or equivalent escaping, followed by subprocess/popen calls using shell=True or /bin/bash -cAffected if The method contains direct concatenation of tool_args into shell command strings without sanitization
-
Check if tool_args from user input reaches the vulnerable functionReview your application code to see if tool_args parameter (from user input, API calls, or config files) is passed to the _substitute_utcp_args methodAffected if User-supplied tool_args values are being passed to the vulnerable method and executed through shell commands
You are affected if python-utcp version is below 1.1.3 AND your application uses tool_args that reach the vulnerable _substitute_utcp_args method with unsanitized input flowing into shell command execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to python-utcp version 1.1.3 or later. If upgrading is not immediately possible, implement input validation and proper shell escaping (e.g., shlex.quote for Unix, appropriate escaping for PowerShell) on all tool_args before inserting them into command strings.
1.1.3
- Upgrade python-utcp to version 1.1.3 or later to remediate the OS command injection vulnerability in the _substitute_utcp_args method in cli_communication_protocol.py
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45369 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data