Obot: MCP Registry API readable without authentication
- Product
- go/github.com/obot-platform/obot
- Affected
- go/github.com/obot-platform/obot < 0.23.0
- Fixed in
- 0.23.0
Last verified against sources: October 26, 2026
Am I affected?
go/github.com/obot-platform/obot: affected go/github.com/obot-platform/obot < 0.23.0. Fixed in 0.23.0.
- Check your version: run
go list -m github.com/obot-platform/obot. Versions < 0.23.0 of github.com/obot-platform/obot are affected. [1]
What to do now
- Upgrade to the fixed version: run
go get github.com/obot-platform/obot@v0.23.0(first patched version 0.23.0). [1] - Upgrade to v0.23.0 or later. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
- In affected versions, turning on registry authentication with OBOT_SERVER_ENABLE_REGISTRY_AUTH=true did not protect the MCP Registry endpoints under /v0.1/*. [1]
- An unauthenticated GET /v0.1/servers returned 200 OK with catalog server metadata. [1]
- The authorizer rejected a fixed set of known-protected prefixes and then allowed everything else, and /v0.1 was not in that set. [1]
- With registry auth disabled, the registry is intentionally public and this is not a defect. [1]
Impact
- An attacker could see the registry server inventory the operator chose to put behind authentication, including names, descriptions, repository URLs, and connect URLs. [1]
- No credential values were exposed. [1]
- Unauthenticated users could not connect to the servers, because connecting is properly protected by auth. [1]
What was done
Sources
- GHSA-pr6h-vr44-xq8j — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
Obot: MCP Registry API readable without authentication
Product: go/github.com/obot-platform/obot | Affected: go/github.com/obot-platform/obot < 0.23.0 | Fixed in: 0.23.0
Summary: In affected versions, turning on registry authentication with OBOT_SERVER_ENABLE_REGISTRY_AUTH=true did not protect the MCP Registry endpoints under /v0.1/*.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/09/ghsa-pr6h-vr44-xq8j-go-github-com-obot-platform-obotCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for go/github.com/obot-platform/obot
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.