CVE-2026-101063 Obot before v0.23.0 Authentication Bypass via Registry API
Unauthenticated attackers can read registry metadata when authentication is enabled due to missing authorization checks on MCP Registry endpoints.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-101063?
CVE-2026-101063 is a medium-severity missing authorization vulnerability in obot-platform obot, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-862
Which versions are affected by CVE-2026-101063?
3 open source packages ship an affected version, including github.com/obot-platform/obot.
| Package | Affected | Fixed in |
|---|---|---|
github.com/obot-platform/obot Go | All versions | 0.23.0 |
github.com/obot-platform/obot Go | All versions | 0.23.0 |
github.com/obot-platform/obot Go | All versions | 0.23.0 |
How do I fix CVE-2026-101063?
Upgrade github.com/obot-platform/obot to 0.23.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-101063 being exploited?
There is no known exploitation of CVE-2026-101063 in the wild and no public exploit code.
Sources
Also known as GHSA-63cq-34vq-4f48, GHSA-pr6h-vr44-xq8j, GO-2026-6525.