# CVE-2026-101065: Obot Docker quickstart unauthenticated admin access

Source: https://junglewise.ai/threats/cve-2026-101065-obot-is-an-open-source-ai-agent-mcp-platform-in-all-versions-up  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-27. Updated: 2026-09-27  
License: CC BY 4.0 with a link back

CVE-2026-101065 · Severity: critical · CVSS 9.8 · Published 2026-09-27

Obot is an open-source AI agent platform that was documented to launch with authentication disabled by default, exposing the web interface and API on port 8080. An attacker on any network that can reach the exposed port gains full administrative access without credentials, allowing them to register malicious AI agents and access the underlying host's Docker system to deploy ransomware or steal data.

Technologies: [Obot Platform Obot](https://junglewise.ai/threats/technologies/obot). Vendors: [Obot Platform](https://junglewise.ai/threats/vendors/obot-platform).

## Quick answers

**Is CVE-2026-101065 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-101065 being exploited in the wild.

**How severe is CVE-2026-101065?** Critical severity, with a CVSS score of 9.8, published 27 September 2026.

**Which products and versions are affected?** Obot Platform Obot up to and including commit d7e6970.

**Is there a fix for CVE-2026-101065?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-101065 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-101065?** Check whether you run Obot Platform Obot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The Docker quickstart command documented in the README starts with OBOT_SERVER_ENABLE_AUTHENTICATION disabled, causing all requests to be mapped to a synthetic "nobody" user with Owner and Admin roles. The configuration also mounts /var/run/docker.sock into the container, giving the MCP runtime backend direct access to the host's Docker daemon. The fix is documentation-only: the quickstart now enables authentication by default, and existing deployments must set OBOT_SERVER_ENABLE_AUTHENTICATION=true before exposure to untrusted networks.

## Affected products

- obot-platform obot up to and including commit d7e6970

## Timeline

- 2026-05-08: disclosed
- 2026-09-27: advisory

## References

- [https://github.com/obot-platform/obot/security/advisories/GHSA-jj4w-pfgv-4mrm](https://github.com/obot-platform/obot/security/advisories/GHSA-jj4w-pfgv-4mrm)
- [https://www.vulncheck.com/advisories/obot-quickstart-docker-deployment-unauthenticated-admin-access](https://www.vulncheck.com/advisories/obot-quickstart-docker-deployment-unauthenticated-admin-access)

## Related threats

- [Obot authentication bypass in CLI login flow](https://junglewise.ai/threats/cve-2026-114662-obot-before-0-26-0-contains-an-authentication-bypass)
- [Obot authorization bypass in MCP composite route](https://junglewise.ai/threats/cve-2026-103758-obot-0-21-1-through-0-24-1-contains-an-authorization-bypass)
- [obot authorization bypass in /mcp-connect endpoint](https://junglewise.ai/threats/cve-2026-101084-obot-versions-before-v0-21-1-fail-to-enforce-access-control)
- [Obot server-side request forgery in remote MCP server registration](https://junglewise.ai/threats/cve-2026-101064-obot-before-v0-23-0-contains-a-server-side-request-forgery)
- [Obot authentication bypass in MCP Registry endpoints](https://junglewise.ai/threats/cve-2026-101063-obot-versions-before-v0-23-0-fail-to-enforce-authentication-on)