Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.3

obot pre‑v0.21.1 lets logged‑in users access restricted MCP

CVE-2026-101084 · published 21 days ago
Summary

Versions of obot earlier than 0.21.1 do not check whether a user is allowed to use the /mcp-connect function. As a result, any user who is signed in and knows a server ID can connect to back‑end MCP servers and possibly change data using stored OAuth credentials. Upgrade obot to version 0.21.1 or later, or apply the vendor's patch, to enforce proper access controls.

What to do
  • Update obot-platform github.com/obot-platform/obot to version 0.21.1.
  • Update obot-platform obot to version 0.21.1 or later.
Affected software
Ecosystem VendorProductAffected versions
– obot-platform obot < 0.21.1
Go obot-platform github.com/obot-platform/obot < 0.21.1
Fix: upgrade to 0.21.1
Original advisory text
obot before v0.21.1 Authorization Bypass via /mcp-connect
obot versions before v0.21.1 fail to enforce Access Control Rules on the /mcp-connect endpoint, allowing any authenticated user to connect to restricted MCP servers if they possess the server ID. Attackers can bypass authorization checks to access and manipulate sensitive backend systems through MCP tool calls using stored OAuth credentials.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.3 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-639Authorization Bypass Through User-Controlled Key
CWE-284Improper Access Control
Timeline
Published27 Sep 2026
Updated19 Oct 2026
First seen27 Sep 2026
Sources
CVE-2026-101084 · NVD
CVE-2026-101084 · MITRE
GHSA-vw82-7fv8-r6gp · OSV
Track software like this
Free during beta