Skip to content

AAK-MCP-OBOT-CVE-2026-101084-001: Obot image below v0.25.0: MCP gateway access-control bypasses, open OAuth client registration, SSRF

Severity
CRITICAL
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
ObotImageGatewayAuthzBypass

What it detects

Obot, a self-hosted MCP gateway, ships as the container image ghcr.io/obot-platform/obot and a Helm chart, so the image tag is the only thing that states which release a deployment runs. Before v0.21.1 the /mcp-connect endpoint does not enforce Access Control Rules, so any authenticated user who has a server ID can connect to an MCP server the administrator restricted to other groups and call its tools with the stored OAuth credentials (CVE-2026-101084, CVSS 3.1 9.6, CWE-639, GHSA-vw82-7fv8-r6gp). v0.21.1 added /mcp-connect/ to the deny list in checkUI, but /mcp-connect-composite/{mcp_id} reaches the same mcpGateway.Proxy without that prefix, so a Basic-role user with a composite MCP ID still gets through (CVE-2026-103758, CVSS 8.1, CWE-863, GHSA-6fwv-3h4c-37j9: 0.21.1 through 0.24.1, no patched version named). Before v0.23.0, with authentication enabled, OAuth dynamic client registration needs no authentication and accepts any redirect URI, and the authorization flow auto-completes for a logged-in user, so one crafted link hands an attacker's client an access token (CVE-2026-101062, CVSS 8.8, CWE-863); and remote MCP server registration fetches any URL a Power User supplies, including internal services and cloud metadata, with the response echoed in error messages (CVE-2026-101064, CVSS 7.6, CWE-918). Also before v0.23.0, with registry authentication enabled, the MCP Registry endpoints under /v0.1/* answer without authentication, so anyone can list server names, descriptions, repository URLs and connect URLs (CVE-2026-101063, CVSS 5.3, CWE-862, GHSA-pr6h-vr44-xq8j). v0.25.0 is the first release whose checkUI authorizes only the UI's own fallback route (obot-platform/obot#7375). v0.24.2, cut from the 0.24 branch after it, still has the 0.24.1 deny list and is reported.

How to fix

Run ghcr.io/obot-platform/obot at v0.25.0 or later and pin that tag (or its digest) in compose files, manifests and Helm values. Until then, expose the gateway only to users trusted with every MCP server behind it, since Access Control Rules do not separate them.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-OBOT-CVE-2026-101084-001

Limitations

Reads image references only: an image: value or any other mention of REPO:TAG in YAML (compose files, Kubernetes manifests, MCP configs), a Helm values mapping of repository (or registry + repository) and tag, Dockerfile and Containerfile FROM, and docker run arguments in *mcp*.json and claude_desktop_config.json. A tag that is not a version (main, main-20250617, dev), a digest with no tag, an interpolated tag (:${VERSION}, {{ .Values.tag }}) and a Helm tag left empty (the chart's appVersion decides) state no version and are not reported. A two-part tag such as 0.24 stands for the newest patch on that line and is reported only when the whole line sits below the fixed version. Mirrors under another registry are not matched, and commented-out lines are skipped. latest (or no tag) is not reported: it was v0.26.2 on 2026-10-03. The enterprise image ghcr.io/obot-platform/obot-enterprise is a different image and is not matched.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-OBOT-CVE-2026-101084-001.md: the page then shows that text, with the registry reference appended under it.