UTC
Medium

Obot: MCP Registry API readable without authentication

GHSA-pr6h-vr44-xq8j · published 2026-09-18

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
No CVE
Fixed in
0.23.0
What it is

Worst case is disclosure of the registry server inventory (names, descriptions, repository URLs, connect URLs) that the operator explicitly chose to put behind authentication. No credential values are exposed and unauthenticated users cannot connect to the servers because connecting is properly protected by auth.

What to do

Upgrade github.com/obot-platform/obot to 0.23.0 or later.

If you cannot upgrade yet

Upgrade to v0.23.0 or later, in which the /v0.1 registry prefix is treated as a protected route so authentication is enforced for unauthenticated callers.

Affected
PackageRegistryAffectedFixed in
github.com/obot-platform/obotGo< 0.23.00.23.0

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].