high CVSS 8.8

CVE-2025-53376·Docker vulnerability

Dokploy is a self-hostable Platform as a Service (PaaS) that simplifies the deployment and management of applications and databases. An authenticated, low-privileged user can run arbitrary OS commands on the Dokploy host. The tRPC procedure docker.getContainersByAppNameMatch interpolates the attacker-supplied appName value into a Docker CLI call without sanitisation, enabling command injection under the Dokploy service account. This vulnerability is fixed in 0.23.7.

Severity
high
Software
Docker
Fixed in
0.23.7
Published
2025-07-07

Affected versions

Until: 0.23.7

Fixed in: 0.23.7

How to fix this CVE

Update Dokploy to version 0.23.7 or later to patch a command injection vulnerability in the docker.getContainersByAppNameMatch tRPC procedure. This vulnerability allows authenticated users with low privileges to execute arbitrary OS commands on the host system by injecting unsanitized input into Docker CLI calls. Immediate patching is critical for any Dokploy deployment accessible to multiple users.

sudo dnf upgrade docker-ce

Defensia detects this vulnerability

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement a Web Application Firewall rule to block POST requests to /trpc/docker.getContainersByAppNameMatch that contain shell metacharacters (semicolon, pipe, ampersand, backtick, dollar sign) in the appName parameter. Example regex pattern: appName.*[;|&`$\n\r]

How to check if you are affected

  1. Step 1: Check the installed Dokploy version by running: docker exec <dokploy-container-name> cat /app/package.json | grep version (or check the admin panel)
  2. Step 2: Verify if the tRPC endpoint /trpc/docker.getContainersByAppNameMatch is accessible by examining Dokploy's API routes and authentication logs
  3. Step 3: Search Docker logs and Dokploy application logs for suspicious appName parameters containing shell metacharacters (;, |, &, $, `, >, <, etc.): grep -E "(;|\||&|\$|\`|>|<)" /var/lib/docker/containers/*/logs.log
  4. Step 4: Verify the fix by confirming the installed version is 0.23.7 or higher and check the git commit hash fb5d2bd matches the deployed code

FAQ

What is CVE-2025-53376?

This is a command injection vulnerability in Dokploy's tRPC procedure that handles Docker container queries. Attackers can inject arbitrary shell commands through the appName parameter, which gets passed directly to Docker CLI without input sanitization.

Is CVE-2025-53376 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities catalog, CVE-2025-53376 is not currently being actively exploited in the wild. However, no public exploit is required due to the straightforward nature of command injection.

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

CVE-2025-53376 affects Dokploy versions prior to 0.23.7. All versions up to and including 0.23.6 contain the vulnerable tRPC procedure.

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

Run the command: docker exec <dokploy-container-name> grep -i version /app/package.json to get the installed version. If it is below 0.23.7, your system is vulnerable.

Does Defensia detect CVE-2025-53376?

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

Related Docker CVEs

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-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-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.
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.

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

Get started free