Skip to main content
Menu
CVEs

CVE

Dokploy unauthorized container access via Docker WebSocket handlers

Only affects Dokploy v0.29.13 through v0.30.8 when a serviceId query parameter is sent to the container WebSocket handlers. Fixed in 0.31.0.

CVE-2026-129316EUVD-2026-129323Published Updated Summary written by a model

9.9CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 0.31.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Dokploy versions v0.29.13 through v0.30.8 Caller sends a serviceId query parameter to the container WebSocket handlers

Summary

Dokploy's Docker terminal, container log, and monitoring WebSocket handlers let a logged-in member with read access to any service reach unrelated containers. Over the network, such a member can get a root shell in the Dokploy panel container, read other tenants' logs and statistics, and use the mounted Docker socket to take over the host.

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

Who should check

Teams running self-hosted Dokploy v0.29.13 through v0.30.8 (including canary) where organization members hold read access to at least one service.

“v0.29.13 – v0.30.8 (latest release)”

github.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.9/10CVSS 9.9
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Dokploy versions v0.29.13 through v0.30.8 Caller sends a serviceId query parameter to the container WebSocket handlers
  • Upgrade to a fixed version: 0.31.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129316 (Dokploy: serviceId lets a member reach any container (Member -> Root) over the docker WebSocket handlers), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129316 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: from 0.29.13, fixed in 0.31.0
Fixed versions: 0.31.0.
Conditions (all must be true for the bug to be hit):
- Dokploy versions v0.29.13 through v0.30.8 (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-pwg8-2x8c-wc2m)
- Caller sends a serviceId query parameter to the container WebSocket handlers (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-pwg8-2x8c-wc2m)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129316 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129316 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-pwg8-2x8c-wc2m
- https://github.com/Dokploy/dokploy/pull/5716
- https://github.com/Dokploy/dokploy/pull/5733
- https://github.com/Dokploy/dokploy/commit/2555b8d91e88b9071a7d6afed84c0ff3b4a3838d
- https://github.com/Dokploy/dokploy/commit/99e4f1c8dc62510b8abd46bd7fd359d6ad61075e
- https://github.com/Dokploy/dokploy/commit/9f6e82abf62ec1cdeb6d0adf7eb8f2fa2fbb076a
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129316
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129316"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Dokploy dokploy

    From 0.29.13 · fixed in 0.31.0

Evidence 9

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129316

Is CVE-2026-129316 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The container WebSocket handlers in Dokploy accept a serviceId query parameter that lets a low-privileged organization member reach containers they should not access. The advisory says this can lead to root on the Docker host and to reading or altering other tenants' containers, logs and data.Source: github.com

Which versions are affected by CVE-2026-129316?

dokploy: from 0.29.13 before 0.31.0.Source: cve.now feed data

Am I affected, and how do I check?

The listed affected versions are Dokploy v0.29.13 through v0.30.8. The issue involves requests to the container WebSocket handlers that include a serviceId query parameter. To check a installation, compare the installed Dokploy version with that range.Source: github.com

How do I fix CVE-2026-129316?

Upgrade Dokploy to 0.31.0 or later, which is the listed fixed version.Source: github.com

More CVEs