The member needs read access to at least one service, which can be a service they created. The CNA record rates the flaw 9.9 Critical under CVSS 3.1.The researcher demonstrated access to the Dokploy panel container, whose mounted Docker socket can extend control to the host. The same boundary failure can expose other containers' logs and application statistics. This is a cross-service privilege escalation, not an unauthenticated entry point.
What it allows
How Does CVE-2026-129316 Cross the Container Boundary?
Dokploy's container terminal, log, and monitoring WebSocket handlers accept a service identifier supplied by the member. The authorization helper checks whether that member can read the named service. The researcher found that it does not consistently verify whether the requested container or application belongs to that service.
A member can therefore present access to one service while requesting a different container. The advisory demonstrates a root shell in the Dokploy panel container and log access to another container. Because the panel container mounts the Docker socket, the advisory describes a path from panel-container control to host-level control. It also describes access to other applications' statistics.
This finding concerns the service-to-container ownership check. CVE-2026-129986, CVE-2026-129987, CVE-2026-129989, and CVE-2026-129991 are separate Dokploy flaws. The earlier GHSA-899j-cjwp-v4gw is related because this advisory calls its fix incomplete; the identifiers are distinct.
Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-129316 from 21 August through 19 November 2026. The measured unit is posts, and this discussion signal does not establish an incident or active exploitation. The vulnerability intelligence platform can help teams prioritize a confirmed deployment exposure.
Who is affected
Which Dokploy Versions Are Affected by CVE-2026-129316?
The CNA affected list covers Dokploy 0.29.13 through versions before 0.31.0 and says the issue is fixed in 0.31.0. The GitHub advisory still lists 0.29.13 through 0.30.8 as affected and leaves its patched-version field empty. Its narrative also mentions a then-current canary build. Treat the CNA's 0.31.0 boundary as the published fix, while recording the advisory discrepancy in change control.
Inventory self-hosted Dokploy panels, their running versions, and the Docker hosts or remote servers they manage. Prioritize deployments where members can read or create services and where the panel has access to the Docker socket. Review member access and unexpected container-terminal or log sessions across service boundaries. A session record warrants investigation but does not, by itself, prove host compromise.
The vulnerability management guide describes documenting a fix and checking the running release. The vulnerability prioritization glossary explains how prerequisites and impact affect triage.
Timeline
-
2026-11-12
The researcher published GHSA-pwg8-2x8c-wc2m with a demonstration on Dokploy 0.30.8.
-
2026-11-18
The CNA published CVE-2026-129316 and listed versions from 0.29.13 to before 0.31.0 as affected.
What to do
-
Inventory Dokploy deployments
Record each self-hosted panel's running version, its managed Docker hosts, and which members can read or create services.
-
Upgrade to the CNA fixed version
Follow the CNA record and upgrade affected Dokploy deployments to 0.31.0 or a later vendor-confirmed fixed release. Record that the GHSA patched-version field is still empty.
-
Verify each running panel
After deployment, verify the version reported by every running Dokploy panel and confirm it is at least 0.31.0. Do not rely only on an image tag or update ticket.
-
Constrain member access until upgraded
Review who can create or read services and reduce unnecessary member access. This limits the stated prerequisite but does not replace the code fix.
-
Investigate suspicious cross-service activity
Review available authentication, terminal, log-access, and Docker audit records for unexpected member activity. Preserve evidence and investigate suspected host access through the incident process.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-129316 in Brandefense Atlas
The Atlas record of CVE-2026-129316: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-129316 require a Dokploy account?
Yes. The advisory requires a member with read access to at least one service, including one the member created.
Why can the flaw affect the Docker host?
The advisory demonstrates access to the Dokploy panel container, which mounts the Docker socket. That socket can give control over the host's containers.
What version fixes CVE-2026-129316?
The CNA record names 0.31.0. The GitHub advisory still has no patched version listed, so record that source discrepancy during verification.
Sources
- Dokploy cross-service container access advisoryGitHub Security Advisory
- CVE-2026-129316 recordGitHub CNA via CVE Program