CVE-2026-101063: medium-severity vulnerability in obot-platform obot
Obot before v0.23.0 Authentication Bypass via Registry API
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.2%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
obot-platform · obotRelated CVEs — obot-platform obot
In the same product, most dangerous first.
CVE-2026-130767MEDIUMObot 0.9.0 before 0.27.0 Command Injection via Docker MCP Server File SetupEPSS 0.6%CVE-2026-101065CRITICALObot Quickstart Docker Deployment Unauthenticated Admin AccessEPSS 0.4%CVE-2026-130765MEDIUMObot before 0.27.0 Open Redirect via Tab Character in rd ParameterEPSS 0.4%CVE-2026-101084CRITICALobot before v0.21.1 Authorization Bypass via /mcp-connectEPSS 0.3%CVE-2026-101062HIGHObot before v0.23.0 Authentication Bypass via OAuth Dynamic Client RegistrationEPSS 0.3%CVE-2026-130764HIGHObot 0.8.0 before 0.27.0 SSRF via OAuth Token EndpointEPSS 0.3%