Read the docs

Obot Quickstart Docker Deployment Unauthenticated Admin Access

Priority MEDIUM 48CWE-306Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-306.

Summary

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 request is mapped to a synthetic "nobody" user that holds the Owner and Admin roles, so any unauthenticated party who can reach the exposed port obtains full administrative access to the Obot API and UI, including the ability to register and launch attacker-controlled MCP servers. Because the quickstart also mounts /var/run/docker.sock into the container, the MCP runtime backend reachable this way has access to the host's Docker control surface. The fix is documentation-only: the quickstart now enables authentication, and operators who followed the previous instructions should set OBOT_SERVER_ENABLE_AUTHENTICATION=true before exposing the host to any untrusted network.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00437 38th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
obot-platformobotall versions—No fix listedCNA
  • obot Vendorobot-platform Affected all versions Fixed in — No fix listed CNA

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-101065
  2. 2026-10-03 Alias added: GHSA-m95h-j2gj-xrgq

References

  • TI-2026-65117 obot before v0.21.1 Authorization Bypass via /mcp-connect CVSS 4.0CRITICAL 9.3
  • TI-2026-65095 Obot before v0.23.0 Authentication Bypass via OAuth Dynamic Client Registration CVSS 4.0HIGH 8.7
  • TI-2026-65757 Obot 0.21.1 through 0.24.1 Authorization Bypass via /mcp-connect-composite/ Route CVSS 4.0HIGH 8.6
  • TI-2026-79161 Authentication bypass in Obot CLI login exposes API keys CVSS 4.0HIGH 8.6
  • TI-2026-65097 Obot before v0.23.0 Server-Side Request Forgery via MCP CVSS 4.0HIGH 8.3
  • TI-2026-65096 Obot before v0.23.0 Authentication Bypass via Registry API CVSS 4.0MEDIUM 6.9
See all 9 →

Sources