Security readout for executives and security teams
Plain-English summary
A low-privilege Dokploy member can abuse volume-backup functionality to run arbitrary commands on the control-plane host. Docker socket access can make the resulting compromise equivalent to host or root control, threatening hosted applications, data, credentials, and service availability.
Executive priority
Treat this as an immediate patching priority for affected Dokploy control planes. A single low-privilege member account could become host-level compromise, creating material confidentiality, integrity, and availability risk across workloads managed by the platform.
Technical view
Before version 0.29.13, volumeName values supplied to volumeBackup.create and volumeBackup.runManually were interpolated without quoting and passed to child_process.exec. This CWE-78 command-injection flaw requires an authenticated low-privilege account, needs no user interaction, and crosses a security boundary through Docker socket access.
Likely exposure
Self-hosted Dokploy installations below 0.29.13 are affected when low-privilege members can access the vulnerable volume-backup operations. Exposure depends on deployed version, account access, and feature availability. The supplied sources identify no other affected products.
Exploitation context
The vulnerability is remotely reachable by an authenticated low-privilege Dokploy member and has a CVSS 3.1 score of 9.9. The supplied bundle says it is not in KEV and provides no evidence of active exploitation. Insider access or a compromised member account could provide the required foothold.
Researcher notes
The core issue is unquoted attacker-controlled input reaching a shell execution sink. Scope changes because Docker socket access can translate application-level command execution into host-equivalent control. The public bundle identifies the fix, pull request, and commit, but does not establish exploitation in the wild.
Mitigation direction
- Upgrade Dokploy to version 0.29.13 or later.
- Restrict low-privilege member access until the upgrade is complete.
- Review and revoke unnecessary Dokploy accounts and sessions.
- Protect administrative access with strong authentication and least privilege.
- Follow the Dokploy advisory for any additional vendor guidance.
Validation and detection
- Confirm every Dokploy control-plane instance reports version 0.29.13 or later.
- Inventory member accounts permitted to use volume-backup functionality.
- Review relevant application and host logs for unexpected backup activity or command execution.
- Assess Docker and host activity for unexplained containers, processes, files, or credential access.
- Verify the deployed build contains the vendor's referenced remediation commit.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupContainer behavior lookup
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.
Open ATT&CK lookupCVE-2026-72901 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-w223-vw9m-4f9cCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Dokploy/dokploy/pull/4873CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Dokploy/dokploy/commit/d629faebc6dcb9d4785f84bf30b2b285f9f59379CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Dokploy/dokploy/releases/tag/v0.29.13CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.