Is CVE-2026-101084 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101084 being exploited in the wild.

How severe is CVE-2026-101084?

Critical severity, with a CVSS score of 9.6, published 27 September 2026.

Which products and versions are affected?

Obot Platform Obot before v0.21.1.

Is there a fix for CVE-2026-101084?

A patch was published on 2026-05-08: v0.21.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101084 attacked?

It is attacked over the network.

Am I affected by CVE-2026-101084?

Check whether you run Obot Platform Obot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101084: obot authorization bypass in /mcp-connect endpoint

CVE-2026-101084 · Severity: critical · CVSS 9.6 · Published 2026-09-27

obot is a platform that manages connections to Model Context Protocol (MCP) servers, which are backend services like HR systems or ticketing systems. 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 know the server ID. An attacker could bypass authorization checks to access and manipulate sensitive backend systems using the platform's stored OAuth credentials, potentially reading or modifying employee records, creating tickets, or accessing other sensitive data.

Technologies: Obot Platform Obot. Vendors: Obot Platform.

Quick answers

Is CVE-2026-101084 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101084 being exploited in the wild.
How severe is CVE-2026-101084?: Critical severity, with a CVSS score of 9.6, published 27 September 2026.
Which products and versions are affected?: Obot Platform Obot before v0.21.1.
Is there a fix for CVE-2026-101084?: A patch was published on 2026-05-08: v0.21.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101084 attacked?: It is attacked over the network.
Am I affected by CVE-2026-101084?: Check whether you run Obot Platform Obot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authorization bypass in the /mcp-connect/{mcp_id} endpoint that fails to enforce Access Control Rules (ACRs). Any authenticated user with low privileges (Basic role or higher) can POST to this endpoint with a known MCP server ID to bypass authorization checks and make tool calls to restricted servers, regardless of ACR membership. The vulnerability occurs because an incorrect UI authorizer component was providing access when it should have been denied; the scope is changed because Obot's stored OAuth credentials grant access to third-party services beyond Obot's authorization scope.

Affected products

obot-platform obot before v0.21.1

Timeline

2026-05-08: disclosed
2026-05-08: patched: v0.21.1 released
2026-09-27: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.