CVE-2026-129316

9.9Critical

Published 18 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite

9.9CVSS

Critical

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
Full C/I/A compromise
Weakness
CWE-862

What an attacker gets

Authenticated users with read access can gain a root shell on the host and access other tenants' data. They achieve this by manipulating WebSocket handlers to target containers outside their authorized scope.

Root cause

The WebSocket handlers fail to validate that the requested containerId or appName belongs to the provided serviceId.

Affected versions

Dokploy 0.29.13 through 0.30.x

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Fix & remediation

Upgrade to Dokploy version 0.31.0 or later. If you cannot patch immediately, restrict access to the Dokploy panel to trusted users only.

remediation — bash
$ docker pull dokploy/dokploy:v0.31.0 && docker-compose up -d

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-129316