CVE-2026-72737: Dokploy: Cross-organization IDOR in Dokploy backup destinations exposes another tenant's S3 credentials and backups
Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.8 and earlier, backup.create, backup.update, and backup.restoreBackupWithLogs in apps/dokploy/server/api/routers/backup.ts accept a client-controlled destinationId and use the referenced destination without verifying that destination.organizationId equals ctx.session.activeOrganizationId. An authenticated member with backup permissions for a service in one organization can cause another organization's S3 accessKey and secretAccessKey to be materialized by packages/server/src/utils/backups/utils.ts getS3Credentials on the attacker's service host, read that organization's backup objects, or redirect and poison backups across tenant boundaries.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Dokployto a version that resolves this vulnerability.Fixed in 0.29.8
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72737?
CVE-2026-72737 has a critical severity rating of 9.6.
What does CVE-2026-72737 affect?
CVE-2026-72737 affects Dokploy versions 0.29.8 and earlier.
What type of vulnerability is CVE-2026-72737?
CVE-2026-72737 is a cross-organization IDOR vulnerability that exposes S3 credentials and backups of other tenants.
How do I fix CVE-2026-72737?
To fix CVE-2026-72737, upgrade to the latest version of Dokploy that resolves this vulnerability.
What consequences does CVE-2026-72737 pose?
CVE-2026-72737 can lead to unauthorized access to another tenant's S3 backups and credentials.