What is the CVSS score of CVE-2026-45663?

CVE-2026-45663 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Dokploy are affected by CVE-2026-45663?

Dokploy versions 0.29.1 and earlier contain a critical vulnerability in the Docker file upload feature that allows authenticated users to execute arbitrary operating system commands on the host…

How to fix or mitigate CVE-2026-45663?

Within 24 hours: Enumerate all Dokploy deployments running 0.29.1 or earlier; restrict file upload feature access to a minimal set of trusted administrators; enable comprehensive audit logging on all file upload operations. Within 7 days: Review upload logs for suspicious destinationPath patterns; implement network segmentation separating Dokploy infrastructure from production workloads and credential stores. Within 30 days: Establish continuous monitoring of GHSA advisory for patch release; develop tested migration plan to patched versions; deploy host-based endpoint detection and response (EDR) as interim control on all Dokploy systems.

Dokploy CVE-2026-45663

EUVD-2026-33348 CRITICAL

Command Injection (CWE-77)

2026-05-29 security-advisories@github.com

Docker File Upload Command Injection

9.9

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 29, 2026 - 16:45 vuln.today

CVE Published

May 29, 2026 - 16:16 nvd

CRITICAL 9.9

DescriptionGitHub Advisory

Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.1 and earlier, a command injection vulnerability exists in the Docker file upload functionality. When an authenticated user uploads a file to a container, the destinationPath parameter is not properly sanitized and is directly interpolated into a shell command string. By including shell metacharacters such as ; or ", an attacker can escape the intended docker cp command and execute arbitrary OS commands on the Dokploy host.

AnalysisAI

Command injection in Dokploy 0.29.1 and earlier allows authenticated users to execute arbitrary OS commands on the host by abusing the Docker file upload feature's unsanitized destinationPath parameter. The CVSS 9.9 score reflects scope change to the underlying host from a containerized context, and no public exploit identified at time of analysis though the GHSA advisory provides sufficient technical detail to reconstruct one.

Technical ContextAI

Dokploy is a self-hostable Platform-as-a-Service that orchestrates Docker containers for application deployment. The vulnerability sits in the file upload workflow that wraps the docker cp command, where user-controlled destinationPath input is concatenated directly into a shell command string rather than passed as an argv array or properly escaped. CWE-77 (Improper Neutralization of Special Elements used in a Command) captures the root cause: shell metacharacters like semicolons and double quotes break out of the intended docker cp invocation, allowing arbitrary command execution under the privileges of the Dokploy process - which typically runs with Docker socket access equivalent to root on the host.

RemediationAI

Patch availability is not independently confirmed from the supplied data - administrators should consult the GitHub Security Advisory at https://github.com/Dokploy/dokploy/security/advisories/GHSA-9m66-74x3-5mwr for the patched release tag and upgrade Dokploy beyond 0.29.1 as soon as that version is published. Until a patched version is deployed, compensating controls include restricting Dokploy account creation and tightly auditing the existing low-privilege user roster (since PR:L is the only barrier), placing Dokploy behind a VPN or IP allowlist to remove network-based reachability, and disabling or proxying the container file upload endpoint at a reverse proxy layer - accepting that this last control will break legitimate file-copy workflows. Monitoring docker cp invocations and process trees spawned by the Dokploy service for anomalous shell activity provides detective coverage during the patch window.