Obot has an authorization bypass in /mcp-connect/{id} that allows any authenticated user to use any registered MCP server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary If you have the MCP Server ID, you can connect to the MCP server even if you don't have permissions to the server. The MCP gateway endpoint /mcp-connect/{mcpid} does not enforce Access Control Rules (ACRs). Any authenticated Obot user who possesses an MCP Server ID can connect to that server through the gateway — including making tool calls — regardless of whether they are a member of any MCP Registry that grants access to the server. In practice this means any User can fully use MCP servers that the administrator believed were restricted to specific groups. Severity Reporter estimate: Critical. | CVSS 3.1 metric | Value | |---|---| | Attack Vector | Network | | Attack Complexity | Low | | Privileges Required | Low (authenticated Obot user, any role ≥ Basic) | | User Interaction | None | | Scope | Changed (Obot authorization bypass enables access to data and operations on an upstream third-party service via Obot's stored OAuth credentials) | | Confidentiality | High | |…

Published by the source

13 May 2026, 15:32 UTC

Last modified by the source

13 May 2026, 15:32 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vw82-7fv8-r6gp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-vw82-7fv8-r6gp

Advisory: Obot has an authorization bypass in /mcp-connect/{id} that allows any authenticated user to use any registered MCP server
IDs: GHSA-vw82-7fv8-r6gp
Record: https://patchnext.com/advisories/ghsa-vw82-7fv8-r6gp (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/obot-platform/obot 0.21.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/obot-platform/obot: affected <= 0.21.0; fixed in 0.21.1

## Suggested inspection (read-only)
- Go github.com/obot-platform/obot: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/obot-platform/obot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vw82-7fv8-r6gp (GitHub-reviewed advisory GHSA-vw82-7fv8-r6gp lists affected ranges: Go github.com/obot-platform/obot >=0 <=0.21.0)

Commands are suggestions: review each one before running it.