# CVE-2026-101084: obot before v0.21.1 Authorization Bypass via /mcp-connect

> Authenticated users can bypass authorization on the /mcp-connect endpoint to access restricted MCP servers and manipulate backend systems.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-g524-9c6h-8w7v, GHSA-vw82-7fv8-r6gp, GO-2026-5678

## What is CVE-2026-101084?

CVE-2026-101084 is a critical missing authorization vulnerability in obot-platform obot, published on 27 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-101084?

3 open source packages ship an affected version, including github.com/obot-platform/obot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/obot-platform/obot` | Go | All versions | 0.21.1 |
| `github.com/obot-platform/obot` | Go | All versions | 0.21.1 |
| `github.com/obot-platform/obot` | Go | All versions | 0.21.1 |

## How do I fix CVE-2026-101084?

Upgrade github.com/obot-platform/obot to 0.21.1 or later.

## Is CVE-2026-101084 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101084 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101084 and fix it if it is affected.

What it is: CVE-2026-101084 is a critical missing authorization vulnerability in obot-platform obot, published on 27 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101084 exists.

Affected packages and fixed versions:
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.21.1
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.21.1
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.21.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101084/ (Markdown: https://insights.sbomify.com/CVE-2026-101084/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101084
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101084
- OSV: https://osv.dev/vulnerability/CVE-2026-101084

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101084/
Summaries are generated and may contain mistakes; the official description above is the record.