Obot Docker Quickstart Exposes API on All Interfaces Without Auth
The Obot AI agent platform Docker quickstart binds to 0.0.0.0:8080 by default, exposing the full API without authentication to any host that can reach the port.
- Vendor
- Obot Platform
- Product
- Obot (all versions through commit d7e6970)
- CVSS
- 9.8
- EPSS (exploit probability)
- 0.4%
- Status
- patched
- Published
Is CVE-2026-101065 being exploited?
Not on any exploited-vulnerability catalog we track. CVE-2026-101065 was not on the CISA, ENISA or CIRCL exploited catalogs as of our 2026-11-13 snapshot. That can change quickly; check the write-up below for the latest reporting.
FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.4% (scored October 14, 2026).
- CISA KEV[ — ]
- ENISA EUVD (exploited)[ — ]
- CIRCL KEV[ — ]
Catalog snapshot 2026-11-13. Full cross-catalog view: /kev-comparison
CVE-2026-101065 timeline
Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON
The Obot README’s Docker quickstart command starts the container listening on 0.0.0.0:8080, binding to all network interfaces without authentication. Any host that can reach that port can access the full Obot API.
Mitigation requires binding to 127.0.0.1 or placing a reverse proxy with authentication in front of the container. The project disclosed this via GitHub Security Advisory GHSA-jj4w-pfgv-4mrm.
Other Obot Platform CVEs we track
| CVE / Vulnerability | Severity | CVSS | EPSS | Added to KEV |
|---|---|---|---|---|
| CVE-2026-101084 Obot /mcp-connect Endpoint Ignores Access Control Ruleswrite-up | [ CRITICAL ] | 9.6 | 0.3% | — |
| CVE-2026-101063 Obot MCP Registry Endpoints Unauthenticated When Auth Is Enabledwrite-up | [ MEDIUM ] | 5.3 | 0.2% | — |
