CVE-2026-101057: universal-tool-calling-protocol python-utcp · Cleartext Transmission
Affects universal-tool-calling-protocol python-utcpSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.1.3 when convenient.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.1.3
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade universal-tool-calling-protocol python-utcp to 1.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| universal-tool-calling-protocolpython-utcp | Affected
| Fixed in
|
PyPIpython-utcppkg:pypi/python-utcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in utcp-mcp version 1.1.3, which implements validation of MCP server URLs to enforce secure connections before any network communication occurs. Users should upgrade to version 1.1.3 or later to remediate this vulnerability.
Description
CVE-2026-101057 is a vulnerability in the utcp-mcp plugin of python-utcp up to version 1.1.2 where it connects to HTTP and WebSocket MCP server URLs without enforcing secure URL validation. This allows cleartext transmission of the MCP handshake to non-secure HTTP servers, potentially exposing sensitive information to network interception. The vulnerability is limited by the fact that the server URLs are operator-configured and the OAuth2 authentication path is not invoked in affected versions. The issue is fixed in version 1.1.3 by validating server URLs before connection.