VulnerabilityPublished 18 Sep 2026

github.com/obot-platform/obot · Obot: MCP Registry API readable without authentication

Affects github.com/obot-platform/obotSource GCVE Database

CVSS 5.3 Medium : upgrade to 0.23.0 when convenient.

Data as of 19 Sep 2026, 01:56 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.23.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

What to do

Upgrade github.com/obot-platform/obot to 0.23.0.

Affected software

Product	Affected	Fixed in
Gogithub.com/obot-platform/obot	Affected <0.23.0	Fixed in 0.23.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

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.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Sep 2026, 01:56 UTC

WeaknessesCWE-862, CWE-863

Technical details

References

Community reviews

Related threats