CVE-2026-101084obot before v0.21.1 Authorization Bypass via /mcp-connect
Updated under an hour ago ()
Does this affect you?
It affects obot-platform obot. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.28%, higher than 19% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 9.6 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- Weakness (CWE)
- CWE-639
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.28% (percentile 19)
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Sep 30, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
obot-platform obot obot_platform:obot (from the name) | before 0.21.1; 0.21.1 not affected | CNA record |
References
- https://github.com/obot-platform/obot/security/advisories/GHSA-vw82-7fv8-r6gpvendor-advisory
- https://www.vulncheck.com/advisories/obot-before-0.21.1-authorization-bypass-via-mcp-connectthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.