/

CVE-2026-72737

Severity:

CRITICAL RISK

(9.6)

Broken Access Control (CWE-639) in Dokploy Backups

CVE-2026-72737

Received

Vulnerability type

Category:

Broken Access Control / Insecure Direct Object Reference

CWE:

CWE-639, CWE-862

Impact:

Cross-tenant credential disclosure, backup data exposure, and backup integrity compromise

Severity:

CRITICAL RISK

(9.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Dokploy improperly trusts a client-supplied destination identifier in backup operations without confirming that the destination belongs to the active organization. An authenticated member with backup permissions may thereby access another tenant's S3-backed backups, expose cloud storage credentials on a service host, or redirect and poison backup data.

Affected context

The issue occurs in Dokploy deployments up to and including the affected release when backup creation, update, or restoration operations accept a destination identifier from the client. Risk is present when the referenced destination is resolved without enforcing an organization-ownership relationship with the active session, particularly where S3 credentials are materialized on a service host for backup processing.

Exploit preconditions

  • Attack surface: Authenticated Dokploy backup API operations
  • Required access: A valid account with backup permissions for a service in one organization
  • Trigger point: A backup create, update, or restore operation that processes a client-controlled destination identifier
  • Why exploitation is possible: Authorization checks do not consistently verify that the selected destination belongs to the active organization, allowing a permitted user to reference a cross-tenant destination

Why this happens

The underlying bug is an object-level authorization failure. Backup handlers accept a destination identifier and use the corresponding destination without binding the lookup and authorization decision to the active organization context.

This maps primarily to CWE-639: Authorization Bypass Through User-Controlled Key, because a user-controlled identifier can select an object outside the user's authorized tenant. It also relates to CWE-862: Missing Authorization, where the required organization ownership check is absent or incomplete.

Potential impact

  • An attacker may obtain another organization's S3 access credentials through backup processing
  • An attacker could read backup objects belonging to another tenant
  • Backup contents may be exposed, including application or operational data
  • Backups could be redirected, overwritten, or poisoned across organization boundaries
  • Compromised credentials may enable further access to the affected storage environment

General mitigation guidance

Mitigation generally focuses on enforcing tenant-aware authorization at every object lookup and backup operation.

Common defensive patterns include:

  • Deriving the organization scope from the authenticated session rather than trusting client-provided organization values
  • Verifying that every destination's organization identifier matches the active organization before use
  • Applying consistent authorization checks to create, update, restore, and related backup workflows
  • Returning only objects that are already filtered by the caller's authorized tenant scope
  • Reducing the privileges and lifetime of materialized storage credentials
  • Separating backup storage by tenant and restricting access to only the required objects
  • Preserving backup integrity through immutable or append-only storage policies where appropriate

How teams detect issues like this

High-level detection can include:

  • Static analysis rules for database or service lookups using client-controlled identifiers without adjacent authorization checks
  • Code review searches for destination, organization, tenant, or resource identifiers accepted directly from request bodies
  • Tests that attempt cross-organization object references for every backup operation
  • Policy enforcement requiring organization-scope predicates on multi-tenant resource queries
  • Audit logging and alerting for backup operations whose requested destination falls outside the session's organization
  • Automated security review tools that identify missing object-level authorization patterns

Sources

SourceLink
github.comgithub.com/Dokploy/dokploy/security/advisories/GHSA-56qv-89fq-3h2q

Frequently asked

questions

Yes, within the application's authenticated attack surface. Exploitation can occur through backup API requests when the caller has valid access and the application fails to enforce destination ownership.

The attacker generally needs an authenticated account with backup permissions for a service in an organization. The account does not need to belong to the organization whose destination is targeted.

Enforce server-side, organization-scoped authorization before resolving or using any backup destination. The check should apply consistently across creation, update, restoration, and related backup paths.

Treat all client-supplied object identifiers as untrusted, require tenant ownership predicates in resource queries, add cross-tenant authorization tests, and limit the privileges of storage credentials used by backup workers.

Find out what's already
exploitable in your codebase.