critical CVSS 9.6

CVE-2025-64419·Docker vulnerability

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.445, parameters coming from docker-compose.yaml are not sanitized when used in commands. If a victim user creates an application from an attacker repository (using build pack "docker compose"), the attacker can execute commands on the Coolify instance as root. Version 4.0.0-beta.445 fixes the issue.

Severity
critical
Software
Docker
Fixed in
4.0.0
Published
2026-01-05

Affected versions

Until: 4.0.0

Fixed in: 4.0.0

How to fix this CVE

Update Docker to version 4.0.0 or later to patch the command injection vulnerability in parameter handling. This fix prevents malicious docker-compose.yaml files from executing arbitrary commands with root privileges on the Docker host. Ensure all systems running affected versions are patched immediately, as exploitation allows complete system compromise.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Docker version: docker --version or docker version | grep -i version
  2. Verify if docker-compose is enabled and applications are loaded from untrusted repositories: docker ps and docker images | grep -E 'repository|tag'
  3. Search system logs for suspicious command execution: grep -r 'docker-compose' /var/log/ and journalctl -u docker -n 1000 | grep -i 'error\|failed\|executed'
  4. Confirm patch installation: docker --version should report 4.0.0 or higher; compare against NVD fixed version

FAQ

What is CVE-2025-64419?

CVE-2025-64419 is a command injection vulnerability in Docker where unsanitized parameters from docker-compose.yaml files are passed directly into system commands. An attacker can craft a malicious docker-compose file that executes arbitrary commands with root privileges when deployed through Coolify.

Is CVE-2025-64419 being actively exploited?

No, CVE-2025-64419 is not currently listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, the attack requires minimal complexity and delivers critical impact, making it attractive to adversaries.

What versions of Docker are affected by CVE-2025-64419?

All Docker versions prior to 4.0.0 are affected. The vulnerability exists in parameter sanitization logic that was corrected in version 4.0.0 and later.

How do I check if my server is vulnerable to CVE-2025-64419?

Run 'docker --version' and compare the output against 4.0.0. If your version is lower, your system is vulnerable. Additionally, audit any docker-compose.yaml files sourced from untrusted repositories for suspicious environment variables or command substitutions.

Does Defensia detect CVE-2025-64419?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2025-64419 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-2025-64419. Free for 1 server.

Get started free