Disclosed weakness · no CVE recorded

Obot users named anonymous could bypass MCP connection permissions

Obot · Obot Platform · MCP gateway

First documented disclosure · Review checkpoint

Summary

An authenticated user could choose the username anonymous and connect to known MCP servers outside their grants.

Severity and exploitation evidence

Critical · 9.6/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed sources establish the weakness or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

MCP connection authorization treated a mutable display username as proof that the caller was unauthenticated.

Conditions required

Authentication is enabled; the attacker has a regular account not managed by SCIM and knows a target server ID.

Potential impact

Unauthorized MCP tool use with stored server configuration, including bypass of selected tools on shared virtual MCP components.

Affected versions and configurations

>= 0.21.1, <= 0.28.1.

Fix and mitigation status

0.28.2 fixes this issue.

Practical next steps

Upgrade to 0.28.2 and review renamed accounts and MCP access. Confirm access policy against authenticated identity rather than account names.

Operating lesson

Use authentication state, not a user-editable name, to identify anonymous callers.

Evidence and limits

The complete advisory was published November 20, after the November 19 release. The maintainer assigns the CVSS score. No CVE is assigned in the reviewed advisory. Tagged production code contains the named correction. Per-user OAuth servers still require the attacker’s own OAuth sign-in; the owner’s upstream tokens are not used. Unrelated server IDs are random and not disclosed by this issue. REST API access is unaffected. The username-only PR appeared November 19; the complete bypass was disclosed November 20.

Sources