No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 07:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Nov 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dokploy
Dokploy dokploy |
|
| Vendors & Products |
Dokploy
Dokploy dokploy |
Wed, 18 Nov 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Dokploy: serviceId lets a member reach any container (Member -> Root) over the docker WebSocket handlers | |
| Weaknesses | CWE-862 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-19T16:58:27.342Z
Reserved: 2026-11-13T22:30:18.286Z
Link: CVE-2026-129316
Updated: 2026-11-19T16:52:21.937Z
Status : Deferred
Published: 2026-11-18T23:17:18.187
Modified: 2026-11-19T17:17:56.940
Link: CVE-2026-129316
No data.
OpenCVE Enrichment
Updated: 2026-11-20T12:00:06Z