CVE-2026-101057

published 27 Sep 2026 · updated 30 Sep 2026

utcp-mcp before 1.1.3 SSRF via unvalidated MCP server URL

3.1LowCVSS 3.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.1.3.

utcp-mcp (the MCP plugin of python-utcp) through 1.1.2 connects to the HTTP and WebSocket MCP server URLs given in a call template's mcpServers configuration without the ensure_secure_url validation that the HTTP-family plugins apply, so the HTTPS/WSS-or-loopback rule is not enforced. A call template naming a plain-HTTP, non-loopback MCP server URL is dialed as configured, exposing the MCP handshake to network interception and permitting cleartext connections to internal hosts. The mcpServers configuration is operator-authored rather than remote data, and the connection is an MCP handshake rather than an arbitrary request returning a body, which limits practical exploitation; the OAuth2 token_url credential path described in the original report was not reachable in the affected versions, because the OAuth2 handler was never invoked and the call template's auth field was not read. Fixed in utcp-mcp 1.1.3, which validates server URLs before any connection is made.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
universal-tool-calling-protocol<1.1.31.1.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-101057 severity on Zeptric[![CVE-2026-101057](https://zeptric.io/badge/cve/CVE-2026-101057.svg)](https://zeptric.io/cve/CVE-2026-101057)