IncidentMCP servers and tools
Obot: the Docker quickstart gave anyone on the network admin rights and the Docker socket
Obot, an open-source AI agent and MCP platform, documented a Docker quickstart that listened on 0.0.0.0:8080 with authentication turned off, so every request got the Owner and Admin roles, and that mounted the host's Docker socket. Anyone who could reach it could register malicious MCP servers and drive the host's Docker daemon. The project fixed its documentation in May (GHSA-jj4w-pfgv-4mrm, credited to Ryan Vonbrubeck); CVE-2026-101065 was published on September 27.
Replay the attack step by step in the Learning Center
How it happened
- The quickstart ran the container on all interfaces with authentication disabled.
- With authentication off, a synthetic user gave every request Owner and Admin rights.
- The container mounted /var/run/docker.sock, so admin access in Obot reached the host's Docker runtime.
Impact
Unauthenticated admin access to the agent platform, malicious MCP servers registered for its users, and control of the host's containers.
The fix
Set OBOT_SERVER_ENABLE_AUTHENTICATION=true before the host is reachable by anyone else, keep the platform off public networks, and do not mount the Docker socket unless you need it.
Lessons
- Quickstarts become production. A default that turns authentication off is a vulnerability.
- Mounting the Docker socket hands the host to whoever controls the container.