# CVE-2026-101065 — obot-platform obot

> As of 2026-09-27, CVE-2026-101065 is a CRITICAL-severity vulnerability in obot-platform obot, CVSS v3.1 9.8. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-101065 as of 2026-09-27; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-09-27

## What is CVE-2026-101065?

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.

The record classifies CVE-2026-101065 under weakness class [CWE-306](https://intel.threadlinqs.com/cwe/CWE-306). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 8 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.8 — CRITICAL (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **CVSS v4.0 base score:** 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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-27

## Is CVE-2026-101065 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **obot-platform**: obot

## How to fix CVE-2026-101065

No vendor patch reference has been recorded for CVE-2026-101065 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-101065

No threat campaign in the Threadlinqs corpus currently references CVE-2026-101065, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org. Last verified by Threadlinqs on 2026-09-28.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/obot-platform/obot/security/advisories/GHSA-jj4w-pfgv-4mrm)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/obot-quickstart-docker-deployment-unauthenticated-admin-access)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-101065
Full detection coverage and IOCs for threats exploiting CVE-2026-101065 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp