Obot-platform vulnerabilities
We track 6 vulnerabilities in Obot-platform products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on October 22, 2026.
Latest Obot-platform vulnerabilities
- 8.1 High severity
obot: Cross-Site Request Forgery
Obot before 0.26.0 contains an authentication bypass vulnerability in the CLI login flow that allows unauthenticated attackers to steal API keys by choosing token request IDs. Attackers can create a token request via POST /api/token-request, send the login lin
- 8.1 High severity
obot: Incorrect Authorization
Obot 0.21.1 through 0.24.1 contains an authorization bypass vulnerability that allows authenticated users to reach MCP servers because the checkUI deny list omits the /mcp-connect-composite/ route. Basic-role users with a composite MCP ID can proxy requests th
- 9.6 Critical severity
obot: Authorization Bypass Through User-Controlled Key
obot versions before v0.21.1 fail to enforce Access Control Rules on the /mcp-connect endpoint, allowing any authenticated user to connect to restricted MCP servers if they possess the server ID. Attackers can bypass authorization checks to access and manipula
- 9.8 Critical severity
obot: Missing Authentication for Critical Functionality
Obot is an open-source AI agent/MCP platform. In all versions up to and including commit d7e6970, the Docker quickstart command documented in the README starts the container listening on 0.0.0.0:8080 with authentication disabled by default. When authentication
- 7.6 High severity
obot: Server-Side Request Forgery
Obot before v0.23.0 contains a server-side request forgery vulnerability in remote MCP server registration that allows privileged users to specify arbitrary URLs without destination validation. Attackers with Power User or higher roles can coerce Obot to make
- 8.8 High severity
obot: Incorrect Authorization
Obot before v0.23.0 (affected versions <= v0.22.1) running with OBOT_SERVER_ENABLE_AUTHENTICATION=true exposes OAuth dynamic client registration without authentication and without any restriction on the redirect URIs a client may register. Because the authoriz