CVE-2026-72868: Dokploy: Member-role RCE as host root via destination.testConnection rclone shell injection
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, apps/dokploy/server/api/routers/destination.ts interpolates the accessKey, secretAccessKey, region, endpoint, provider, and bucket fields from destination.testConnection into an rclone ls command executed through child_process.exec. The `withPermission("destination", "create")` path permits a low-privileged organization member to reach the mutation, close a quoted argument with a crafted field, and execute arbitrary commands in the root Dokploy container, which has access to the host Docker socket. This issue is fixed in version 0.29.13.
Security readout for executives and security teams
Plain-English summary
A low-privileged Dokploy organization member can abuse destination connection testing to run commands inside the root Dokploy container. Because that container can access the host Docker socket, compromise may extend to the host and deployed workloads. Dokploy versions before 0.29.13 are affected.
Executive priority
Treat this as an immediate patching priority. A compromised member account could become a platform-wide and host-level incident, potentially affecting application confidentiality, integrity, availability, secrets, and deployed customer workloads.
Technical view
User-controlled destination fields are interpolated into an rclone command executed by child_process.exec. Insufficient authorization permits members with destination creation access to reach the vulnerable mutation. Crafted input can cause OS command injection in the root container, with Docker-socket access enabling broader host compromise.
Likely exposure
Self-hosted Dokploy instances below 0.29.13 are exposed when an untrusted or compromised organization member can create destinations and reach destination.testConnection. The bundle does not establish how commonly that permission is assigned or whether individual deployments expose management interfaces publicly.
Exploitation context
CVSS 3.1 scores this 9.9 because exploitation is network-reachable, low-complexity, requires only low privileges, and needs no user interaction. The supplied record is not in KEV, and the source bundle provides no evidence of active exploitation.
Researcher notes
The vulnerability combines CWE-78 command injection with CWE-862 missing authorization. The critical boundary is from destination creation permission to command execution through child_process.exec; Docker-socket access materially increases impact. The bundle identifies 0.29.13 as fixed but does not document exploitation telemetry.
Mitigation direction
Upgrade every Dokploy instance to version 0.29.13 or later.
Until upgraded, restrict destination creation to trusted administrators.
Limit Dokploy management access to trusted networks and identities.
If compromise is suspected, rotate credentials accessible from Dokploy, Docker, and hosted workloads.
Review the vendor advisory and release notes before completing remediation.
Validation and detection
Inventory all Dokploy instances and record their running versions.
Confirm each instance reports version 0.29.13 or later.
Review organization roles for members permitted to create destinations.
Inspect relevant logs for suspicious destination.testConnection activity and unexpected child processes.
Investigate Docker and host activity if suspicious connection tests are identified.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.