Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-101065 – Unauthenticated Admin Access & Host Compromise – Obot Quickstart Docker Deployment

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-101065 is a missing-authentication vulnerability (CWE-306) affecting Obot, an open-source AI agent/MCP platform. The Docker quickstart deployment documented in the project’s README starts the Obot container listening on 0.0.0.0:8080 with authentication disabled by default, mapping every incoming request to a synthetic "nobody" user that holds both Owner and Admin roles. The issue is rated critical (CVSS 9.3), since any network party that can reach the exposed port obtains full administrative control over the Obot API and UI with no credentials required.

Technical details

  • Root cause: The documented Docker quickstart command runs Obot with authentication disabled by default and binds the service to all network interfaces (0.0.0.0:8080).
  • Trigger conditions: An operator follows the README’s quickstart instructions and exposes the resulting container to an untrusted network without setting OBOT_SERVER_ENABLE_AUTHENTICATION=true.
  • Attack vector: Network — no authentication or user interaction is required; the attacker only needs to reach the exposed port.
  • Impact: Unauthenticated attackers are treated as an Owner/Admin "nobody" user, granting full access to the Obot API and UI and the ability to register and launch attacker-controlled MCP servers. Because the quickstart deployment also mounts the host’s /var/run/docker.sock into the container, an attacker who reaches the MCP runtime backend can control the host’s Docker environment, potentially leading to full host compromise.

Affected software

  • Obot (obot-platform/obot) — all versions up to and including commit d7e6970, deployed via the documented Docker quickstart configuration with authentication disabled.

Severity

  • CVSS v4.0 Base Score: 9.3 (Critical) — 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
  • 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

Mitigation and recommended actions

  • Immediate: No code patch has been released; the fix is documentation-only. Set the environment variable OBOT_SERVER_ENABLE_AUTHENTICATION=true on all Obot deployments before exposing the service to any network.
  • If authentication cannot be enabled immediately: Do not expose Obot instances running with authentication disabled to untrusted or public networks; restrict access to 127.0.0.1/trusted internal networks only, and avoid mounting /var/run/docker.sock into internet-reachable containers.
  • Review and update any existing Docker quickstart deployments against the latest quickstart documentation, which now enables authentication by default.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge