Disclosed weakness · no CVE recorded

Obot MCP URL templates could send administrator-set credentials to another host

Obot · Obot Platform · MCP gateway

First documented disclosure · Review checkpoint

Summary

A permitted catalog user could alter a templated remote MCP destination and receive its administrator-set headers.

Severity and exploitation evidence

Medium · 6.3/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed sources establish the weakness or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

User-controlled host-template values were substituted without preserving the administrator’s URL structure and domain.

Conditions required

A remote catalog entry permits a user-supplied host variable, has static administrator-set headers, and is granted to a user who should not know those values.

Potential impact

Exposure of shared API keys or bearer tokens attached to that entry and their upstream authority.

Affected versions and configurations

>= 0.12.0, <= 0.28.1.

Fix and mitigation status

0.28.2 fixes this issue.

Practical next steps

Upgrade to 0.28.2 and inspect affected templates; do not attach shared secrets to templates that intentionally permit an arbitrary full host. Rotate exposed upstream credentials.

Operating lesson

Bind shared credentials to an administrator-approved destination after every substitution.

Evidence and limits

The complete advisory was published November 20, after the November 19 release. The maintainer assigns the CVSS score. No CVE is assigned in the reviewed advisory. Tagged production code contains the named correction. Fixed URLs, hostname restrictions and option-only variables are excluded by the advisory. Per-user OAuth is not affected. Entire-host templates intentionally remain unrestricted. This differs from the earlier API disclosure of static headers.

Sources