Quick answers
- Is CVE-2026-45628 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45628 being exploited in the wild.
- How severe is CVE-2026-45628?
- Critical severity, with a CVSS score of 9.6, published 29 May 2026.
- Which products and versions are affected?
- Dokploy <= 0.29.2.
- Is there a fix for CVE-2026-45628?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45628 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45628?
- Check whether you run Dokploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Dokploy (v0.29.2 and earlier) is vulnerable to OS command injection because it uses JavaScript template literals to construct shell commands for Git and Docker operations. These commands are executed via 'child_process.exec()', which invokes a shell (/bin/sh -c). User-supplied inputs, including branch names, repository URLs, and Docker credentials, are interpolated directly into these strings without escaping. An authenticated attacker with application create/edit privileges can inject shell metacharacters (e.g., semicolons) to achieve remote code execution. Because Dokploy typically has access to the Docker socket, this can lead to full host compromise. While a 'shEscape()' function exists in the codebase, it was not applied to the deployment pipeline paths.
Affected products
- Dokploy Dokploy <= 0.29.2
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD