Obot: MCP Registry API readable without authentication
Obot versions up to 0.22.1 with registry authentication enabled do not properly enforce authentication on the MCP Registry API endpoints under /v0.1/*. This allows unauthenticated users to read registry server metadata such as names, descriptions, repository URLs, icons, and connect URLs. No secret credentials or environment variables are exposed, and connecting to servers remains protected by authentication. The issue is fixed in version 0.23.0 and later.
AI Analysis
Technical Summary
In affected Obot versions (<=0.22.1) with OBOT_SERVER_ENABLE_REGISTRY_AUTH=true, the MCP Registry API endpoints under the /v0.1 prefix remain accessible without authentication due to an authorization logic flaw. The authorizer only protects a fixed set of prefixes and does not include /v0.1, allowing anonymous GET requests to retrieve server metadata. Although the registry handler filters data per user, unauthenticated callers can still obtain non-sensitive server inventory information. This vulnerability was addressed in version 0.23.0 by treating /v0.1 as a protected route requiring authentication.
Potential Impact
Disclosure of server inventory metadata that operators intended to protect behind authentication. This includes server names, descriptions, repository URLs, icons, and connect URLs. No sensitive credentials or environment variables are exposed, and unauthenticated users cannot connect to the servers. The impact is limited to information disclosure of non-secret data.
Mitigation Recommendations
Upgrade to Obot version 0.23.0 or later, where the /v0.1 registry prefix is properly protected and requires authentication. This fixes the authorization bypass allowing unauthenticated read access. No other mitigations are necessary as the vulnerability is addressed by the official fix.
Obot: MCP Registry API readable without authentication
Description
Obot versions up to 0.22.1 with registry authentication enabled do not properly enforce authentication on the MCP Registry API endpoints under /v0.1/*. This allows unauthenticated users to read registry server metadata such as names, descriptions, repository URLs, icons, and connect URLs. No secret credentials or environment variables are exposed, and connecting to servers remains protected by authentication. The issue is fixed in version 0.23.0 and later.
CVSS v3.1
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In affected Obot versions (<=0.22.1) with OBOT_SERVER_ENABLE_REGISTRY_AUTH=true, the MCP Registry API endpoints under the /v0.1 prefix remain accessible without authentication due to an authorization logic flaw. The authorizer only protects a fixed set of prefixes and does not include /v0.1, allowing anonymous GET requests to retrieve server metadata. Although the registry handler filters data per user, unauthenticated callers can still obtain non-sensitive server inventory information. This vulnerability was addressed in version 0.23.0 by treating /v0.1 as a protected route requiring authentication.
Potential Impact
Disclosure of server inventory metadata that operators intended to protect behind authentication. This includes server names, descriptions, repository URLs, icons, and connect URLs. No sensitive credentials or environment variables are exposed, and unauthenticated users cannot connect to the servers. The impact is limited to information disclosure of non-secret data.
Mitigation Recommendations
Upgrade to Obot version 0.23.0 or later, where the /v0.1 registry prefix is properly protected and requires authentication. This fixes the authorization bypass allowing unauthenticated read access. No other mitigations are necessary as the vulnerability is addressed by the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pr6h-vr44-xq8j
- Osv Schema Version
- 1.4.0
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6aade53055bf5e2cf5edc2ee
Added to database: 09/19/2026, 01:28:16 UTC
Last enriched: 09/19/2026, 01:56:33 UTC
Last updated: 09/19/2026, 02:54:03 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.