# CVE-2026-101057: utcp-mcp before 1.1.3 SSRF via unvalidated MCP server URL

> An attacker with control over operator-authored configurations can force the library to connect to internal hosts via unvalidated URLs, bypassing security checks.

- **Severity:** Low 2.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:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-vr54-j4qq-9vj9

## What is CVE-2026-101057?

CVE-2026-101057 is a low-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-101057?


## How do I fix CVE-2026-101057?

No fix has been published for CVE-2026-101057 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101057 being exploited?

There is no known exploitation of CVE-2026-101057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101057 and fix it if it is affected.

What it is: CVE-2026-101057 is a low-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101057 in the wild and no public exploit code.

Affected product: universal-tool-calling-protocol python-utcp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101057/ (Markdown: https://insights.sbomify.com/CVE-2026-101057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101057
- OSV: https://osv.dev/vulnerability/CVE-2026-101057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101057/
Summaries are generated and may contain mistakes; the official description above is the record.