# CVE-2026-101065: Obot Quickstart Docker Deployment Unauthenticated Admin Access

> Unauthenticated attackers can gain full admin access and execute code via Docker socket if the quickstart deployment is used without enabling authentication.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-m95h-j2gj-xrgq

## What is CVE-2026-101065?

CVE-2026-101065 is a critical authentication bypass vulnerability in obot-platform obot, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-101065?


## How do I fix CVE-2026-101065?

No fix has been published for CVE-2026-101065 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101065 being exploited?

There is no known exploitation of CVE-2026-101065 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101065 and fix it if it is affected.

What it is: CVE-2026-101065 is a critical authentication bypass vulnerability in obot-platform obot, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101065 in the wild and no public exploit code.

Affected product: obot-platform obot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101065/ (Markdown: https://insights.sbomify.com/CVE-2026-101065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101065
- OSV: https://osv.dev/vulnerability/CVE-2026-101065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101065/
Summaries are generated and may contain mistakes; the official description above is the record.