Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Five Dokploy Host-Compromise Paths Compared

Dokploy vulnerabilities span container access, mounts, passwords, builds, and backups. Compare member permissions, fixed versions, and post-update checks.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
19 November 2026
Reading time
5 min read
Five application paths approaching a protected server boundary

Dokploy vulnerabilities disclosed in November 2026 expose five different paths from an authenticated member to a privileged execution context. The paths involve container access, file mounts, database passwords, Nixpacks builds, and backups. Dokploy’s GitHub advisories rate each CVE 9.9 under CVSS 3.1. Those records and NVD give no CVSS 4.0 score.

These are permission-dependent flaws, not anonymous access to a public web endpoint. A member needs access to a service or application and the relevant action. The distinction matters when deciding which roles and workflows to restrict while installing the update.

Dokploy Vulnerabilities Compared by Entry Condition

The table separates the permission boundary from the action that reaches privileged code, which helps teams use a vulnerability intelligence platform to prioritize exposure. It also separates the vendor’s advisory patch field from a practical update target. Check your running version and role assignments before treating any row as applicable.

Five paths, five required actions
CVEAccess requiredTrigger and potential reach
CVE-2026-129316Read access to one serviceContainer terminal, logs or stats can cross the service boundary; panel container access can reach the host.
CVE-2026-129986Create and delete file mounts on an accessible serviceLocal file-mount deletion reaches a host shell; no running container is needed.
CVE-2026-129987Permission to change a database passwordPassword update reaches a shell command with Dokploy process privileges.
CVE-2026-129989Application build-setting accessA Nixpacks deployment uses the publish directory in a host command.
CVE-2026-129991Backup permission on a serviceA backup run or retention cleanup reaches a privileged command on the host or remote server.

The container-access flaw, CVE-2026-129316, is an authorization failure. The advisory says Dokploy checked whether a member could read one service, then failed to bind the requested container or application to that service. Terminal access could reach the Dokploy panel container, which mounts the Docker socket; logs and statistics could expose other services.

The advisory calls this an incomplete fix of an earlier GHSA. That relationship describes the failed boundary; it does not make the two advisories interchangeable. Review terminal, log, and monitoring access separately when checking the patched deployment.

For CVE-2026-129986, the local file-mount deletion path passes a member-controlled file path into a shell command without safe quoting. A member with mount create and delete permissions can trigger execution on deletion. The advisory emphasizes that a container need not be running.

CVE-2026-129987 concerns database password changes across MySQL, PostgreSQL, MariaDB, MongoDB, and Redis. The validation permits a shell substitution character, and Dokploy interpolates the password into a command string. An authorized password change may therefore run code with the Dokploy process’s privileges, typically root.

CVE-2026-129989 requires access to an application’s build settings. An unrestricted Nixpacks publish-directory value enters a shell command when deployment runs. In contrast, CVE-2026-129991 sits in a backup prefix and can trigger during a manual or scheduled backup, or during retention cleanup. The backup advisory covers database, Compose, and web-server backup paths.

Which Dokploy Version Addresses Each Path?

Four GitHub advisories list versions before 0.31.1 as affected and 0.31.1 as patched. The service-identity advisory instead lists 0.29.13 through 0.30.8 as affected and leaves its patched-version field empty. NVD describes CVE-2026-129316 as fixed in 0.31.0, while Dokploy’s 0.31.0 release notes include container-ownership changes.

CVE GitHub advisory affected range GitHub advisory patched version
CVE-2026-129316 0.29.13 to 0.30.8 None listed
CVE-2026-129986 Before 0.31.1 0.31.1
CVE-2026-129987 Before 0.31.1 0.31.1
CVE-2026-129989 Before 0.31.1 0.31.1
CVE-2026-129991 Before 0.31.1 0.31.1

The blank patch field for CVE-2026-129316 should remain visible in change records. It does not prove that 0.31.0 or 0.31.1 is vulnerable; it means the advisory and NVD do not express the fix identically. For a deployment exposed to all five paths, 0.31.1 or a later vendor release is the common update target, followed by a service-ownership check.

What Should Operators Check After Updating?

First inventory Dokploy panel instances and managed servers, then confirm the version actually running on each. Our external attack surface management page explains the asset visibility needed for that inventory. Prioritize instances where ordinary members can create services, change builds, manage mounts, or configure backups.

After updating, test with a low-privilege account that has access to only one service. Confirm it cannot open another service’s terminal, logs, or monitoring data. Separately verify that file-mount deletion, database password changes, Nixpacks deployment, and backup jobs still work for authorized users. These are our operational checks derived from the five advisories, not vendor test instructions.

Review the access granted to members while the rollout completes. A member’s ability to create a service does not imply authorization to reach other containers. The LXD and Incus isolation analysis provides a separate example of why the boundary between a workload and its host deserves explicit testing.

Brandefense Blackhole counted one dark-chat post mentioning each of CVE-2026-129316, CVE-2026-129986, and CVE-2026-129987 from 21 August through 19 November 2026. Each count measures posts for that identifier; the sets may overlap and must not be added. The posts are research signals, not evidence of an incident or exploitation.

Use the CVSS, EPSS, and KEV signal guide when recording risk decisions. The 9.9 ratings describe potential impact and prerequisites in a scoring model. They do not establish that an unauthenticated attacker reached a Dokploy host or that these flaws were used in the field.

Frequently Asked Questions

Do these Dokploy flaws allow anonymous access?

The five advisories describe authenticated access with service, application, mount, database, or backup permissions. They do not describe an anonymous entry path.

Which Dokploy version should operators install?

Four advisories name 0.31.1 as the patched version. Use 0.31.1 or a later vendor release, then verify the service-boundary behavior for CVE-2026-129316.

Why does CVE-2026-129316 have no patched version in the table?

Its GitHub advisory leaves the patched-version field empty. NVD says 0.31.0 fixes it, and Dokploy 0.31.0 release notes describe container-ownership changes.

Sources

  1. Dokploy advisory: CVE-2026-129316
  2. Dokploy advisory: CVE-2026-129986
  3. Dokploy advisory: CVE-2026-129987
  4. Dokploy advisory: CVE-2026-129989
  5. Dokploy advisory: CVE-2026-129991
  6. Dokploy v0.31.0 release notes
  7. Dokploy v0.31.1 release notes
  8. NVD: CVE-2026-129316
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →