Skip to main content
Menu
CVEs

CVE

Dokploy remote command execution in file mount deletion

Affects Dokploy before 0.31.1 on local (non-remote) services, where file mount deletion runs on the Dokploy host. Fixed in 0.31.1.

CVE-2026-129986EUVD-2026-129324Published Updated Summary written by a model

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

Do first: Check whether your setup matches what the bug needs. Dokploy versions before 0.31.1 (the advisory lists all versions up to and including canary @ v0.29.14 as affected) The file mount belongs to a local (non-remote) service, so deletion runs on the Dokploy host itself rather than a remote server

Summary

Dokploy, a self-hostable Platform as a Service, is affected. An attacker who has a logged-in account with file-mount create and delete permissions can send a request over the network and run arbitrary commands on the host by deleting a local file mount.

Original description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, mount.deleteFileMount passes a path containing the user-controlled filePath to the local removeFileOrDirectory helper, which interpolates it unquoted into rm -rf, while the remote branch is quoted. An authenticated member with file-mount create and delete permissions can execute arbitrary commands in the host context immediately when deleting a local file mount, without requiring a running container. This issue is fixed in version 0.31.1.

Who should check

Teams running self-hosted Dokploy before 0.31.1 with local file mounts, and members who can create and delete mounts on services

“Affected: all versions including canary @ v0.29.14 (latest).”

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 before 0.31.1 (the advisory lists all versions up to and including canary @ v0.29.14 as affected) The file mount belongs to a local (non-remote) service, so deletion runs on the Dokploy host itself rather than a remote server
  • Upgrade to a fixed version: 0.31.1.

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-129986 (Dokploy: OS Command Injection via filePath in mount.deleteFileMount → HOST RCE), 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-129986 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Dokploy versions before 0.31.1 (the advisory lists all versions up to and including canary @ v0.29.14 as affected) (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-945r-hp2m-928m)
- The file mount belongs to a local (non-remote) service, so deletion runs on the Dokploy host itself rather than a remote server (source: https://github.com/Dokploy/dokploy/pull/5907)
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-129986 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129986 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-945r-hp2m-928m
- https://github.com/Dokploy/dokploy/pull/5907
- https://github.com/Dokploy/dokploy/commit/861a1fbfc9f847b706cae65c5312655a53eb8f7c
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
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-129986
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-129986"}.

Timeline

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

Affected versions

  • Dokploy dokploy

    fixed in 0.31.1

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Dokploy/dokploy · Advisory GHSA-945r-hp2m-928m
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129986
RecordNVD · CVE-2026-129986
Other links 3
RepositoryGitHub · Dokploy/dokploy · Pull request #5907
RepositoryGitHub · Dokploy/dokploy · Commit 861a1fbf
RepositoryGitHub · Dokploy/dokploy · Release v0.31.1

Corrections

None so far.

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

Questions about CVE-2026-129986

Is CVE-2026-129986 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 deleteFileMount procedure passes a filePath value into an OS command without proper handling, so an authenticated user can run arbitrary commands in the Docker-privileged host context, which leads to root on the node.Source: github.com, github.com

Which versions are affected by CVE-2026-129986?

dokploy: before 0.31.1.Source: cve.now feed data

Am I affected, and how do I check?

Dokploy versions before 0.31.1 are affected, and the advisory lists all versions up to and including canary v0.29.14. The issue applies to file mounts on local (non-remote) services, where deletion runs on the Dokploy host itself rather than a remote server. Check the installed Dokploy version and whether the service is local.Source: github.com, github.com

How do I fix CVE-2026-129986?

Upgrade Dokploy to version 0.31.1.Source: github.com, github.com

More CVEs