Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

CVE-2026-129316: Dokploy members can reach any container and host

CVE-2026-129316 · published today
Summary

In Dokploy versions from 0.29.13 up to 0.31.0, the web tools that show a terminal, logs, or monitoring data let a user choose a service identifier without properly checking which container belongs to that service. As a result, a user who can view one service could connect to any other container, see other tenants' data, run commands with full rights, and even control the underlying server. Upgrade to Dokploy 0.31.0 or later to have the proper checks in place.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
dokploy dokploy >= 0.29.13, < 0.31.0
Original advisory text
Dokploy: serviceId lets a member reach any container (Member -> Root) over the docker WebSocket handlers
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.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
9.9 Critical
Type
CWE-862Missing Authorization
Timeline
Published18 Nov 2026
Updated18 Nov 2026
First seen18 Nov 2026
Sources
CVE-2026-129316 · MITRE
Track software like this
Free during beta