Quick answers
- Is CVE-2026-45630 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45630 being exploited in the wild.
- How severe is CVE-2026-45630?
- Critical severity, with a CVSS score of 9, published 29 May 2026.
- Which products and versions are affected?
- Dokploy <= 0.28.8.
- Is there a fix for CVE-2026-45630?
- 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-45630 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45630?
- 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
An OS command injection vulnerability exists in the `application.updateTraefikConfig` tRPC endpoint within Dokploy. The root cause is the lack of sanitization for the `traefikConfig` input, which is subsequently interpolated into a shell `echo` command executed via SSH in the `writeConfigRemote` function. An attacker with admin or owner privileges can use a single quote to break out of the shell quoting context and inject arbitrary commands. This results in remote code execution (RCE) with the privileges of the SSH user on managed servers.
Affected products
- Dokploy Dokploy <= 0.28.8
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD