medium CVSS 6.5 EPSS <0.1%

CVE-2026-41369·Docker vulnerability

OpenClaw before 2026.3.31 contains insufficient environment variable sanitization in host exec operations, failing to filter package, registry, Docker, compiler, and TLS override variables. Attackers can exploit this by injecting malicious environment variables to override critical system configurations and compromise host execution integrity.

Severity
medium
Software
Docker
Fixed in
2026.3.31
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 13% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

Until: 2026.3.31

Fixed in: 2026.3.31

How to fix this CVE

Update Docker to version 2026.3.31 or later to patch the environment variable sanitization flaw in host exec operations. This vulnerability allows authenticated attackers to inject malicious environment variables that override critical system settings like package managers, registries, and TLS configurations. Immediate patching is recommended for production environments where Docker host execution is used.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Docker version: docker --version
  2. Query the Docker daemon for active host exec processes: docker ps --filter status=running --format 'table {{.ID}}\t{{.Command}}'
  3. Search Docker daemon logs for suspicious environment variable injections: sudo journalctl -u docker -n 1000 | grep -i 'env\|override\|package\|registry'
  4. Verify the patched version is running after update: docker --version should show 2026.3.31 or higher

FAQ

What is CVE-2026-41369?

CVE-2026-41369 is a medium-severity vulnerability in Docker's host exec implementation that fails to properly sanitize environment variables, allowing authenticated attackers to inject variables that override critical system configurations including package managers, container registries, and TLS settings.

Is CVE-2026-41369 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities (KEV) list, CVE-2026-41369 is not currently being actively exploited in the wild, and no public proof-of-concept exploit is available.

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

All Docker versions prior to 2026.3.31 are vulnerable. The vulnerability was patched in Docker 2026.3.31 and later versions.

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

Run `docker --version` and compare the output against version 2026.3.31. If your version is lower, your installation is vulnerable.

Does Defensia detect CVE-2026-41369?

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

Related Docker CVEs

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.
CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
CVE-2026-44181CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.
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.

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-41369. Free for 1 server.

Get started free