Live Active security incident? Get immediate response
CVE Record

CVE-2026-12210: universal-tool-calling-protocol python-utcp utcp-gql/utcp-websocket server-side request forgery

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.

MediumCVSS 6.5Not KEV-listed Updated
Glexia's Take moderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-12210 is a server-side request forgery issue in python-utcp 1.1.0 affecting utcp-gql/utcp-websocket. A remote authenticated attacker may be able to make the server send unintended requests, potentially reaching internal resources. Public exploit information is reported, but active exploitation is not confirmed by KEV or the provided sources.

Executive priority

Treat as a moderate-priority exposure review. Prioritize internet-facing or internally privileged deployments because SSRF can bridge network boundaries. Since no patch is named in the provided sources, focus on confirming usage, reducing reachability, and monitoring until vendor guidance is available.

Technical view

The issue is classified as CWE-918 SSRF in universal-tool-calling-protocol python-utcp 1.1.0. VulDB reports network attack vector, low complexity, required authentication, and partial confidentiality, integrity, and availability impact. The affected function is not identified in the source bundle, and no vendor fix is documented there.

Likely exposure

Exposure is likely limited to environments running python-utcp 1.1.0 with utcp-gql or utcp-websocket reachable by authenticated users. Internet-facing deployments or services with access to internal networks carry higher business risk.

Exploitation context

The source bundle states an exploit is public and may be used. It does not provide evidence of active exploitation, and the CVE is not marked KEV. Authentication is indicated by the CVSS vector, reducing but not removing risk.

Researcher notes

Evidence is primarily from VulDB and referenced GitHub issues. The affected function is unspecified, vendor response is reported absent, and remediation is not documented in the source bundle. Avoid assuming broader version impact beyond python-utcp 1.1.0.

Mitigation direction

  • Check vendor repository and advisories for an official fix or guidance.
  • Restrict access to utcp-gql and utcp-websocket endpoints to trusted users and networks.
  • Limit server egress to required destinations only.
  • Avoid exposing affected services directly to the internet where possible.
  • Monitor for unexpected outbound requests from affected servers.

Validation and detection

  • Inventory systems using universal-tool-calling-protocol python-utcp.
  • Confirm whether version 1.1.0 is deployed.
  • Identify use of utcp-gql or utcp-websocket components.
  • Review network exposure and authentication requirements for affected endpoints.
  • Check logs for unusual outbound requests from the service host.
Prepared
Confidence
medium
Sources
9

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-12210 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4 CVSS vectors
6 Timeline events
0 ADP providers
8 Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

Score Version Severity Vector Exploit Impact Source
6.5 CVSS 2.0 Medium AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 8 6.4 VulDB
6.3 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
6.3 CVSS 3.0 Medium CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
5.3 CVSS 4.0 Medium CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P VulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.3 Medium
CVSS 4.0 vector shape for CVE-2026-12210 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
universal-tool-calling-protocol python-utcp 1.1.0 Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.