Skip to content

Product

obot-platform github.com/obot-platform/obot vulnerabilities

15 published CVES affecting obot-platform github.com/obot-platform/obot, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
15
Critical
2
High
7
Medium
5
Low
1
Unscored
0
CISA KEV
0

Latest obot-platform github.com/obot-platform/obot CVEs

Newest publication first

  1. HighCVSS 8.3 EPSS 0.32%

    Obot from 0.8.0 before 0.27.0 contains a server-side request forgery vulnerability that allows Power User accounts to reach internal hosts by advertising a malicious OAuth token endpoint in remote MCP server metadata. Attackers can direct token exchange or refresh requests, inclu...

  2. HighCVSS 8.6 EPSS 0.17%

    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 link to a signed-in use...

  3. CriticalCVSS 9.3 EPSS 0.44%

    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 is disabled, every...

  4. CriticalCVSS 9.3 EPSS 0.35%

    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 manipulate sensitive backend...

  5. HighCVSS 8.3 EPSS 0.24%

    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 requests to internal...

  6. MediumCVSS 6.9 EPSS 0.24%

    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...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.