GHSA-vw82-7fv8-r6gp: Github.com/obot platform/obot Obot Has An Authorization Bypass Vulnerability
CRITICALGHSA-vw82-7fv8-r6gp is a CRITICAL (CVSS 9.6) obot has an authorization bypass vulnerability (CWE-284: Improper Access Control) affecting Github.com/obot platform/obot libraries in the Go ecosystem. The issue involves obot has an authorization bypass in /mcp-connect/{id} that allows any authenticated user to use any registered mcp server. Remediation is available by upgrading affected packages to version 0.21.1.
GHSA-vw82-7fv8-r6gp at a Glance
Security Impact
CVSS: 9.6
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).
How to Fix GHSA-vw82-7fv8-r6gp
To remediate this vulnerability, upgrade all affected Github.com/obot platform/obot dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/obot-platform/obot to 0.21.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/obot-platform/obot
How to Check if You Are Affected
To determine whether your application is affected by GHSA-vw82-7fv8-r6gp, inspect your project dependencies for Github.com/obot platform/obot:
inspect dependencies for github.com/obot-platform/obot
Analyze the terminal output to locate any version of Github.com/obot platform/obot in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.21.1), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Github.com/obot platform/obot, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-vw82-7fv8-r6gp Affected Github.com/obot platform/obot Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/obot-platform/obot
|
Go |
< 0.21.1
|
0.21.1
|
References
Frequently Asked Questions
What is GHSA-vw82-7fv8-r6gp?
Which Github.com/obot platform/obot versions are affected?
What version fixes GHSA-vw82-7fv8-r6gp?
Is github.com/obot-platform/obot affected?
What is the CVSS score of GHSA-vw82-7fv8-r6gp?
What CWE is associated with GHSA-vw82-7fv8-r6gp?
How can I check Go dependencies for GHSA-vw82-7fv8-r6gp?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vw82-7fv8-r6gp",
"modified" : "2026-05-13T15:32:11Z",
"published" : "2026-05-13T15:32:11Z",
"aliases" : [ ],
"summary" : "Obot has an authorization bypass in /mcp-connect/{id} that allows any authenticated user to use any registered MCP server",
"details" : "## Summary\n\nIf you have the MCP Server ID, you can connect to the MCP server even if you don't have permissions to the server.\n\nThe MCP gateway endpoint `/mcp-connect/{mcp_id}` 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.\n\nIn practice this means any User can fully use MCP servers that the administrator believed were restricted to specific groups.\n\n## Severity\n\nReporter estimate: **Critical**.\n\n| CVSS 3.1 metric | Value |\n|---|---|\n| Attack Vector | Network |\n| Attack Complexity | Low |\n| Privileges Required | Low (authenticated Obot user, any role ≥ Basic) |\n| User Interaction | None |\n| Scope | Changed (Obot authorization bypass enables access to data and operations on an upstream third-party service via Obot's stored OAuth credentials) |\n| Confidentiality | High |\n| Integrity | High (many MCP servers expose write tools — e.g. `updateEmployee`, `submitTimeoffRequest`, ticket creation, file writes) |\n| Availability | None |\n| **Vector** | `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N` |\n| **Score** | **9.3 / Critical** |\n\nThe upstream impact depends on which MCP servers are deployed and what scope their stored credentials hold; the bound is \"everything the platform's stored OAuth/API credentials can reach.\"\n\n## Affected Versions\n\nConfirmed on `obot v0.21.0`.\n\n## Vulnerability Details\n\nThe intended flow is that a user's authorization is checked during the OAuth process with Obot.\n\n1. The user connects to an MCP URL through Obot.\n2. During the callback, after the user logs into Obot, Obot checks that the user has access to the provided resource (the `/mcp-connect` URL in this case). Obot correctly determines the user's authorization during this flow.\n3. However, another authorization check (the UI authorizer, in this case) was erroneously providing access.\n\n## Reproduction\n\nTested on `obot v0.21.0`.\n\n**Setup:**\n\n1. Configure a multi-user MCP server connected to a sensitive backend — e.g. an HR system, ticketing system, or any service whose stored OAuth token grants broad read/write access. Note its ID.\n4. Create an MCP Registry / Access Control Rule that grants this server **only** to a small group (e.g. two HR employees). Remove the `everyone` group from the relevant rule.\n5. Create or identify a Basic User who is **not** a member of any registry granting access to this server.\n\n**Exploit:**\n\n6. Sign in as the Basic User.\n7. Verify the UI does not list the server in any connector picker (it does not — that path is correctly gated).\n8. Manually craft and call the gateway URL:\n\n ```\n POST https://<obot>/mcp-connect/<mcp_server_id>\n Authorization: <session cookie or API key>\n Content-Type: application/json\n\n {\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}\n ```\n\n9. Observe a successful response listing the server's tools.\n10. Issue an actual tool call:\n\n ```json\n {\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\n \"params\":{\"name\":\"<sensitive_tool>\",\"arguments\":{...}}}\n ```\n\n11. Observe the call succeeds, returning data scoped only by the **upstream** MCP server's OAuth credentials — not by Obot's ACRs.\n\nThe exploit works equally well via Claude Desktop / Claude Code / any MCP-aware client by configuring the gateway URL as a remote MCP endpoint with the user's API key.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/obot-platform/obot"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.21.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.21.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/obot-platform/obot/security/advisories/GHSA-vw82-7fv8-r6gp"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/obot-platform/obot"
}, {
"type" : "WEB",
"url" : "https://github.com/obot-platform/obot/releases/tag/v0.21.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-284" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-13T15:32:11Z",
"nvd_published_at" : null
}
}