In this article
Dokploy flaw rated CVSS 9.9 critical by NVD
NVD rates CVE-2026-129316 in Dokploy at 9.9 out of 10 on CVSS 3.1, which is critical. The bug sits in the Docker terminal, container-log and monitoring WebSocket handlers.
The exploitation status is unknown: the NVD record does not say whether attacks are happening. Treat the update as urgent.
Dokploy 0.29.13 up to 0.31.0 is exposed
NVD lists Dokploy versions from 0.29.13 up to 0.31.0 as affected. Dokploy is a self-hostable PaaS, and its panel container has the Docker socket mounted.
To check your exposure, look at your Dokploy version and see whether it falls in that range. The attacker only needs a member account with read access to any service.
How a read-only member reaches the Docker socket
The handlers take a caller-supplied serviceId as proof of authorization. They do not consistently tie the requested containerId or appName to that service. So a member can point the request at containers that belong to other services.
The CVSS vector shows the flaw is reachable over the network, with low complexity, low privileges and no user interaction. The scope is changed. An attacker can read other tenants' container logs and statistics.
An attacker can also get a root shell in the Dokploy panel container. From there, the mounted Docker socket lets them compromise the host.
Upgrade Dokploy to 0.31.0 now
Upgrade to Dokploy 0.31.0, which fixes the flaw. No workaround is given for anyone who cannot upgrade right away.
The NVD record gives no disclosure or patch release date, and it lists the CVE status as Deferred. Fix references point to commits 2555b8d, 99e4f1c and 9f6e82a, pull requests 5716 and 5733, the v0.31.0 release tag and advisory GHSA-pwg8-2x8c-wc2m.
| Product | Affected | Fixed |
|---|---|---|
| Dokploy | 0.29.13 up to 0.31.0 | 0.31.0 |
Sources
Image: Estormiz, CC0 1.0, via Wikimedia Commons
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].




Discussion