Quick answers
- Is CVE-2026-45633 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45633 being exploited in the wild.
- How severe is CVE-2026-45633?
- Critical severity, with a CVSS score of 9.9, published 29 May 2026.
- Which products and versions are affected?
- Dokploy <= 0.26.6.
- Is there a fix for CVE-2026-45633?
- 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-45633 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45633?
- 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
A command injection vulnerability exists in Dokploy versions 0.26.6 and earlier within the `/docker-container-logs` WebSocket endpoint. The application fails to validate the `tail` and `since` parameters, which are directly concatenated into a shell command string used to fetch Docker logs via `spawn(shell, ["-c", command])`. An authenticated attacker can use shell metacharacters (e.g., semicolons) to break out of the intended command and execute arbitrary OS commands as the root user. This vulnerability is particularly severe because Dokploy often has the Docker socket mounted, potentially facilitating container escape and full host compromise. At the time of reporting, a patch was pending in version 0.26.7.
Affected products
- Dokploy Dokploy <= 0.26.6
Timeline
- 2026-01-27: other: v0.26.6 released with partial fix
- 2026-01-30: other: Incomplete validation discovered by SHENYI Team
- 2026-05-29: disclosed: CVE published