Dokploy
: serviceId lets a member reach any container (Member -> Root) over the docker WebSocket handlers
Not on CISA's list of exploited flaws, and not in the news we track.
CVE-2026-129316Critical9.9
Severity
9.9of 10, critical
Black Shard's team can check your exposure to CVE-2026-129316 and take the fix off your plate.
Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host. This issue is fixed in version 0.31.0.
Updated 19 Nov 2026, 14:06 UTC, 32 of 36 sources answering.
Black Shard's team can check your exposure, take a fix off your plate or step in on a live incident.