high CVSS 8.8

CVE-2026-24763·Docker vulnerability

OpenClaw (formerly Clawdbot) is a personal AI assistant you run on your own devices. Prior to 2026.1.29, a command injection vulnerability existed in OpenClaw’s Docker sandbox execution mechanism due to unsafe handling of the PATH environment variable when constructing shell commands. An authenticated user able to control environment variables could influence command execution within the container context. This vulnerability is fixed in 2026.1.29.

Severity
high
Software
Docker
Fixed in
2026.1.29
Published
2026-02-02

Affected versions

Until: 2026.1.29

Fixed in: 2026.1.29

How to fix this CVE

Update Docker to version 2026.1.29 or later to patch a command injection vulnerability in the sandbox execution mechanism. The vulnerability allows authenticated users to manipulate environment variables and achieve arbitrary command execution within containers. Apply updates immediately to all Docker installations, especially those running OpenClaw or similar containerized AI assistants.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check installed Docker version with `docker --version` or `docker version --format='{{.Server.Version}}'`
  2. Step 2: Verify if OpenClaw or similar tools are running in Docker with `docker ps -a | grep -i openclaw` and check their process environment with `docker inspect <container_id> | grep -A 20 'Env'`
  3. Step 3: Review Docker daemon logs for unusual PATH manipulations: `journalctl -u docker -n 1000 | grep -i 'PATH\|env\|command'` or check `/var/log/docker.log` for execution anomalies
  4. Step 4: Confirm patch application by verifying version is >= 2026.1.29 and reviewing commit 771f23d in the running Docker binary metadata

FAQ

What is CVE-2026-24763?

A command injection vulnerability in Docker's sandbox execution affecting OpenClaw where improper PATH environment variable handling allows authenticated users to inject and execute arbitrary commands within the container. This requires authentication and direct environment variable control but poses high risk due to unrestricted code execution capabilities.

Is CVE-2026-24763 being actively exploited?

No, this vulnerability is not currently tracked as actively exploited in CISA's KEV catalog and no public exploits are available. However, the high CVSS score (8.8) warrants immediate patching.

What versions of Docker are affected by CVE-2026-24763?

All Docker versions prior to 2026.1.29 are affected. The exact earliest vulnerable version is unknown, but all deployments should upgrade to 2026.1.29 or later.

How do I check if my server is vulnerable to CVE-2026-24763?

Run `docker --version` and compare the version number against 2026.1.29. If your version is earlier than 2026.1.29, your Docker installation is vulnerable. Additionally, check `docker info | grep 'Server Version'` for confirmation.

Does Defensia detect CVE-2026-24763?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-24763 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-24763. Free for 1 server.

Get started free