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

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

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

Dokploy versions 0.29.2 and earlier contain a critical command injection vulnerability (CVSS 9.6) allowing authenticated users with application create/edit permissions to execute arbitrary shell…

Dokploy CVE-2026-45628

Q: How to fix or mitigate CVE-2026-45628?

Within 24 hours: Inventory all Dokploy deployments and identify users with application create/edit permissions. Within 7 days: Restrict application create/edit permissions to a minimal set of trusted administrators; implement input validation on branch names, repository URLs, and Docker credential fields if possible through configuration. Within 30 days: Monitor vendor advisory GHSA-3frc-cfh9-ch2c for patch availability and plan immediate upgrade upon release; evaluate alternative deployment platforms if no patch timeline is provided by vendor.

EUVD-2026-33360 CRITICAL

Improper Input Validation (CWE-20)

2026-05-29 GitHub_M

Docker Information Disclosure

9.6

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

9.6 CRITICAL

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

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:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

May 29, 2026 - 17:54 vuln.today

CVE Published

May 29, 2026 - 16:33 nvd

CRITICAL 9.6

DescriptionGitHub Advisory

Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.2 and earlier, Dokploy constructs shell commands using JavaScript template literals and executes them via child_process.exec() (which runs through /bin/sh -c). User-supplied branch names, repository URLs, and Docker credentials are interpolated directly into these commands without escaping. This requires an authenticated user with application create/edit privileges.

AnalysisAI

Command injection in Dokploy 0.29.2 and earlier allows authenticated users with application create/edit permissions to execute arbitrary shell commands on the host by injecting metacharacters into branch names, repository URLs, or Docker credentials. The flaw stems from unsanitized template-literal interpolation passed to child_process.exec(), and at time of analysis no public exploit identified at time of analysis, but the vendor security advisory GHSA-3frc-cfh9-ch2c documents the issue.

Technical ContextAI

Dokploy is a self-hostable Platform-as-a-Service written in Node.js/TypeScript that orchestrates Docker deployments from Git sources. The affected code path uses Node's child_process.exec() - which spawns a shell via /bin/sh -c - and builds the command string with JavaScript template literals that interpolate user-controlled values (branch name, repository URL, Docker registry credentials) without shell-escaping or switching to the safer execFile()/spawn() argument-array form. This pattern is the textbook trigger for CWE-20 (Improper Input Validation) leading to OS command injection: any shell metacharacter ($(), backticks, ;, &&, |, newline) embedded in those fields is parsed by the shell rather than treated as data. The CPE cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* confirms all versions of the Dokploy application are in scope up to the fix.

RemediationAI

Upstream fix available (advisory GHSA-3frc-cfh9-ch2c); released patched version not independently confirmed from the supplied data, so consult https://github.com/Dokploy/dokploy/security/advisories/GHSA-3frc-cfh9-ch2c for the exact post-0.29.2 release tag and upgrade to that or later. Until the patched build is deployed, restrict the Dokploy admin/UI to trusted operators only - disable self-registration, audit and remove unnecessary accounts holding application create/edit privileges, and place the panel behind a VPN or IP allowlist (trade-off: blocks legitimate remote operators and CI integrations that hit the API directly). As a defensive control on the host, run the Dokploy process as a low-privileged user inside a hardened container with the Docker socket scoped via a proxy such as docker-socket-proxy rather than mounted raw, so a successful injection still cannot trivially escape to root on the host (trade-off: some Dokploy features that require broad Docker API access may break and need explicit allowlisting).