CVE-2026-12210
Deferred Deferred - Pending Action
Server-Side Request Forgery in Python-utcp 1.1.0

Publication date: 2026-06-15

Last updated on: 2026-06-15

Assigner: VulDB

Description
A vulnerability was detected in universal-tool-calling-protocol python-utcp 1.1.0. This affects an unknown function of the component utcp-gql/utcp-websocket. Performing a manipulation results in server-side request forgery. The attack can be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-15
Last Modified
2026-06-15
Generated
2026-06-17
AI Q&A
2026-06-15
EPSS Evaluated
2026-06-16
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
universal-tool-calling-protocol python-utcp 1.1.0
universal-tool-calling-protocol python-utcp From 1.1.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The vulnerability in python-utcp version 1.1.0 affects the utcp-gql and utcp-websocket components. It is caused by improper localhost security validation that relies on string prefix matching rather than verifying the actual hostname or IP address.

This flaw allows attacker-controlled domains such as 127.0.0.1.attacker-domain.com to bypass localhost checks because the code only checks if URLs start with certain localhost prefixes instead of confirming the hostname is truly a loopback address.

As a result, an attacker can manipulate endpoint URL configurations to perform server-side request forgery (SSRF), sending requests to remote servers while bypassing security controls.

Impact Analysis

Exploiting this vulnerability can lead to several security impacts including unauthorized disclosure of sensitive information.

  • Leakage of authorization headers and API keys to attacker-controlled servers.
  • Exposure of internal tool-call data and request content.
  • Bypassing security controls that rely on localhost validation.

The attack can be initiated remotely without prior authentication but requires the attacker to control or influence the endpoint URL input.

Detection Guidance

This vulnerability can be detected by identifying if the system or network is using python-utcp version 1.1.0, specifically the utcp-gql or utcp-websocket components, and if it improperly validates localhost URLs using string prefix matching rather than proper hostname parsing.

Detection involves checking for usage of URLs that start with localhost or 127.0.0.1 but may actually resolve to remote hosts due to crafted domain names like 127.0.0.1.attacker-domain.com or 127.0.0.1.x.x.x.sslip.io.

Suggested commands include network monitoring or log inspection to find requests with suspicious localhost-prefixed domains that do not resolve to loopback addresses.

  • Use DNS resolution commands to verify if localhost-prefixed domains resolve to non-loopback IPs, e.g., `nslookup 127.0.0.1.attacker-domain.com` or `dig 127.0.0.1.x.x.x.sslip.io`.
  • Inspect application logs or network traffic for requests to URLs starting with 'http://localhost/' or 'http://127.0.0.1/' that contain unexpected domain suffixes.
  • Use packet capture tools like `tcpdump` or `Wireshark` to monitor outgoing requests from the vulnerable components and check for suspicious hostnames.
Mitigation Strategies

Immediate mitigation steps include restricting access to the vulnerable python-utcp version 1.1.0 and preventing untrusted input from controlling endpoint URLs.

Specifically, ensure that URL validation uses a proper URL parser to strictly verify that hostnames are exactly localhost, 127.0.0.1, or ::1, rather than relying on string prefix matching.

If possible, upgrade to a patched version of python-utcp that addresses this validation bypass.

  • Implement input validation to reject crafted domains that appear to be localhost but resolve externally.
  • Add regression tests or monitoring to detect malicious localhost variations.
  • Limit network access and firewall rules to prevent unauthorized external requests originating from the vulnerable components.
Compliance Impact

The vulnerability in python-utcp 1.1.0 allows attackers to bypass localhost validation and perform server-side request forgery (SSRF), potentially leading to unauthorized disclosure of sensitive information such as authorization headers, API keys, and internal tool-call data.

Such unauthorized disclosure of sensitive data could impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information from unauthorized access and leakage.

Because the vulnerability enables attackers to send authenticated requests to attacker-controlled infrastructure and leak sensitive headers and request content, organizations using affected versions may face risks related to data confidentiality and integrity, which are critical for regulatory compliance.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12210. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart