Dokploy: member compose command and raw file reach host root (CVE-2026-72884 fix incomplete)
Severity: critical · Patch status: partial · Since 2026-07-21 · CVE-2026-72865, CVE-2026-72867, CVE-2026-72884
A researcher's oss-sec writeup dated 2026-11-21 describes two ways a non-owner organisation member with service:create access can reach host root through Dokploy's compose feature, tested on v0.31.2. The first bypasses the CVE-2026-72884 command validator: sanitizeCommand rejects shell metacharacters and checks chained segments after the first one, but never validates the first token, so a command beginning with a docker run that mounts the host root filesystem passes unchanged; the validator code is the same at v0.31.2 and v0.31.4. The second is the raw compose file path, which writes the supplied YAML without a privileged, capadd or host-mount check. The researcher reports live tests on their own Docker setup; these were not independently reproduced. The vendor advisories cover CVE-2026-72884, CVE-2026-72865 and CVE-2026-72867, all fixed in 0.29.13, and no vendor advisory or fix covering the first-token bypass or the raw-file path has been found. CISA's SSVC entry lists exploitation of CVE-2026-72884 as proof-of-concept; it is not in CISA KEV and no in-the-wild exploitation has been reported.
What to do
- Restrict service:create and compose deploy rights to trusted admins.
- Block privileged, cap_add and host-path mounts in raw compose files until the vendor ships a complete fix.
- Update to a release containing the 0.29.13 fixes and watch the Dokploy advisories for the first-token bypass.
Fixed versions
- 0.29.13 (advisory fixes for CVE-2026-72884, -72865, -72867; the first-token bypass is still present at v0.31.4 in source)
Sources
All live incidents on Threat Watch