CVE-2026-101063: Obot before v0.23.0 Authentication Bypass via Registry API
Obot versions before v0.23.0 fail to enforce authentication on MCP Registry endpoints under /v0.1/ when registry authentication is enabled. Unauthenticated attackers can read registry metadata including server names, descriptions, repository URLs, and connect URLs by sending GET requests to /v0.1/servers.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Obotto a version that resolves this vulnerability.Fixed in v0.23.0
Event History
Frequently Asked Questions
Which deployments are exposed?
Obot deployments running a version before v0.23.0 are exposed when registry authentication is enabled. The affected endpoints are MCP Registry API paths under /v0.1/*.
What does an attacker need to exploit this issue?
An attacker only needs network access to the affected Obot Registry API. No credentials or user interaction are required; a GET request to /v0.1/servers can retrieve registry metadata.
What information can be obtained?
Unauthenticated requests can disclose registry metadata, including server names, descriptions, repository URLs, and connect URLs. The provided data does not indicate modification, deletion, or service-disruption impact.
How can I check whether my deployment is affected?
Confirm whether the Obot version is earlier than v0.23.0 and whether registry authentication is enabled. Then test whether an unauthenticated GET request to /v0.1/servers returns registry metadata.