Dokploy
Dokploy before 0.31.1 OS Command Injection via Compose Backup serviceName
Dokploy before 0.31.1 contains an OS command injection vulnerability in getComposeContainerCommand() that allows authenticated organization members to execute shell commands via the serviceName parameter. Attackers can store serviceName values with shell metacharacters through backup.create or backup.update tRPC procedures, executing commands as root when scheduled backups run and taking over the host via the mounted Docker socket.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.31.1
Fixed in 0.31.1
Mitigation
Upgrade dokploy to 0.31.1 or later.
References
- Vendor advisory github.com/Dokploy/dokploy/security/advisories…
- Patch github.com/Dokploy/dokploy/pull/5908
- Patch github.com/Dokploy/dokploy/commit/b24006e16e95…
1 more
- Release notes github.com/Dokploy/dokploy/releases/tag/v0.31.…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 suspicious or fake
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| GHLists/new-cves | 24 Sep 2026 −51 d | 0 | Suspicious · score 60
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.