Security readout for executives and security teams
Plain-English summary
Dokploy 0.29.8 and earlier has a tenant-isolation flaw in backup destination handling. A logged-in user with backup permissions in one organization may access another organization’s S3 backup credentials and backup data, or interfere with backups across organizations. This is most urgent for multi-tenant Dokploy deployments.
Executive priority
Treat as urgent for any shared or multi-organization Dokploy environment. The business risk is exposure of cloud storage credentials and backups between tenants. Single-organization deployments may have lower practical impact but should still validate version and vendor guidance.
Technical view
The backup.create, backup.update, and backup.restoreBackupWithLogs paths accept a client-controlled destinationId without confirming destination.organizationId matches ctx.session.activeOrganizationId. This is an IDOR/missing authorization issue mapped to CWE-639 and CWE-862, with CVSS 9.6. The flaw can expose S3 accessKey and secretAccessKey via getS3Credentials and enable cross-tenant backup access or poisoning.
Likely exposure
Exposed systems are Dokploy deployments running version 0.29.8 or earlier, especially where multiple organizations or tenants use backup destinations. Exploitation requires an authenticated member with backup permissions for a service in one organization.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The attack is low complexity after authentication and can cross tenant boundaries, affecting confidentiality and integrity of S3-backed backups.
Researcher notes
The key authorization gap is destinationId trust across backup router methods. Evidence identifies affected versions and vulnerable code paths, but the provided sources do not include exploit-in-the-wild confirmation or a named fixed release.
Mitigation direction
- Identify all Dokploy instances and confirm whether they run 0.29.8 or earlier.
- Review Dokploy’s GitHub advisory and vendor guidance for fixed versions or official workarounds.
- Restrict backup permissions to trusted users until remediation is applied.
- Audit backup destinations and S3 credentials for unexpected cross-organization use.
- Rotate S3 credentials if cross-tenant exposure is suspected.
Validation and detection
- Inventory Dokploy version across production, staging, and shared environments.
- Check whether Dokploy is configured with multiple organizations or tenants.
- Review users with backup permissions in each organization.
- Inspect logs for unusual backup create, update, or restore activity involving backup destinations.
- Verify vendor remediation has been applied once official guidance is available.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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.
Open ATT&CK lookupCVE-2026-72737 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.6 (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:N
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:N3.15.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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-56qv-89fq-3h2qCVE 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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.