Obot MCP Registry Endpoints Unauthenticated When Auth Is Enabled
Obot before v0.23.0 does not enforce authentication on MCP Registry endpoints at /v0.1/* even when registry auth is configured, exposing server listings to unauthenticated callers.
- Vendor
- Obot Platform
- Product
- Obot (before v0.23.0)
- CVSS
- 5.3
- EPSS (exploit probability)
- 0.2%
- Status
- patched
- Published
When registry authentication is enabled in Obot, affected releases still allow unauthenticated requests to the MCP Registry API under /v0.1/*. A remote caller can query /v0.1/servers and read catalog metadata such as server names, descriptions, repository URLs, and connection URLs without supplying credentials.
The advisory says the flaw exposes registry information but does not expose credential values or let an unauthenticated caller connect to a listed server. That narrower impact is reflected in the medium-severity rating. Deployments running Obot through v0.22.1 with OBOT_SERVER_ENABLE_REGISTRY_AUTH=true are affected.
Upgrade to Obot v0.23.0 or later. The fixed release treats the /v0.1 registry prefix as a protected route and enforces authentication before returning registry data. The issue was disclosed as GitHub Security Advisory GHSA-pr6h-vr44-xq8j.
