Security readout for executives and security teams
Plain-English summary
A logged-in Dokploy user with permission to create or update service file mounts can make Dokploy run unauthorized operating-system commands on managed servers. In default deployments, this can provide full remote control of the host, risking data theft, service disruption, and compromise of workloads sharing that server.
Executive priority
Treat this as an immediate remediation priority on production or externally reachable Dokploy systems. A permitted user could convert application access into control of managed hosts. Contain risky permissions and SSH reachability now, then apply the vendor-supported remediation after confirming it in the advisory.
Technical view
Dokploy 0.28.8 and earlier improperly handles shell metacharacters in the filePath value used for service file mounts. An authenticated, low-privileged user can trigger blind OS command injection, with Dokploy executing attacker-controlled commands over SSH on the configured managed server. The issue is classified as CWE-78 and CVSS 3.1 score 9.9.
Likely exposure
Exposure exists where Dokploy 0.28.8 or earlier permits authenticated users to create or update service file mounts. Risk is greatest when Dokploy can access production managed servers over SSH. Internet exposure increases credential-attack opportunities, but authentication and file-mount permissions are still required.
Exploitation context
The supplied sources describe a network-reachable, low-complexity attack requiring authentication but no user interaction. Successful exploitation can affect confidentiality, integrity, and availability beyond Dokploy itself. The bundle does not establish active exploitation, and CVE-2026-72882 is not identified as a CISA KEV entry.
Researcher notes
The CVSS vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, reflecting authenticated network exploitation and impact crossing a security boundary. The injection is blind, so lack of visible command output does not eliminate risk. The provided bundle names affected versions but does not explicitly name a fixed version or confirm exploitation in the wild.
Mitigation direction
- Identify and prioritize every Dokploy instance running version 0.28.8 or earlier.
- Check the Dokploy advisory for the vendor-supported fixed release or mitigation.
- Restrict file-mount creation and updates to trusted administrators until remediation is complete.
- Limit Dokploy SSH access to only necessary managed servers and privileges.
- Review and disable unnecessary or suspicious Dokploy accounts and sessions.
Validation and detection
- Inventory Dokploy versions and record all instances at version 0.28.8 or earlier.
- Confirm which roles and accounts can create or update service file mounts.
- Map every managed server reachable from Dokploy over SSH.
- Review file-mount changes for unexpected filePath values or unexplained modifications.
- Examine managed-server audit data for unusual commands or processes associated with Dokploy access.
- After remediation, verify the installed version against the vendor advisory.
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 lookupCVE-2026-72882 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-qcf5-jjjp-7794CVE reference, GitHub_M · x_refsource_CONFIRM
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.