Dokploy v0.31.2 lets members reach host root via compose
Original title: Dokploy: the fix checks the characters, never the first word — a member's compose command and raw compose file both reach host root, 9.9 each (v0.31.2, live-proven)
A non-admin member can use a custom command or a raw compose file; earlier validators miss both paths.
An oss-security post says Dokploy's compose feature still lets a member reach the host as root through two inputs. A command-field validator and a privilege guard on structured service definitions were added in 2026, but neither covers the path it was attached to. The stated precondition is a non-owner, non-admin member. No fixed version appears in the snippet.
Unconfirmed: Scores, live proof, and incomplete member preconditions are the poster's claims; no CVE or fix is stated.
- theknell posted the report on November 21.
- The reporter scores each path 9.9.
- The issue was demonstrated against v0.31.2.
- Inputs are a custom command and a raw compose file.
Impact: member reaches host root via compose inputs
| Product | Affected |
|---|---|
| Dokploy | v0.31.2 |
- ATT&CK
- T1611 Escape to Host
- Vendors
- Dokploy
From the original article
Posted by theknell on Nov 21 Two doors, same room. Dokploy's compose feature gives a member two ways to describe a deployment: type a custom command, or supply the compose file raw. The vendor hardened this feature in the 2026 disclosure rounds — the command field got a validator, the structured service definition got a privilege guard.
seclists.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.