CVE-2026-101065: obot · Missing Authentication
Affects obotSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| obot-platformobot | Affected
| Fixed in– |
AI-suggested
The vendor has issued a documentation-only fix that enables authentication by default in the Docker quickstart setup. Operators who followed the previous instructions should set the environment variable OBOT_SERVER_ENABLE_AUTHENTICATION=true before exposing the service to any untrusted network. This mitigates the risk by requiring authentication for all requests.
Description
CVE-2026-101065 is a critical vulnerability in the obot open-source AI agent platform. The Docker quickstart command, as documented in the README for all versions up to and including commit d7e6970, starts the container with authentication disabled by default and listens on 0.0.0.0:8080. This allows any unauthenticated user who can reach the exposed port to gain full administrative access to the Obot API and UI. The vulnerability is exacerbated by the mounting of /var/run/docker.sock into the container, giving attackers control over the host's Docker environment. The fix is documentation-only, requiring operators to enable authentication by setting OBOT_SERVER_ENABLE_AUTHENTICATION=true before exposing the service to untrusted networks.