What is the CVSS score of CVE-2026-72737?

CVE-2026-72737 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.2%.

Which versions of Dokploy are affected by CVE-2026-72737?

Dokploy 0.29.8 and earlier contains a critical authorization flaw that allows organization members with backup permissions to access S3 credentials and backup data from other organizations,…

How to fix or mitigate CVE-2026-72737?

Within 24 hours: inventory all Dokploy deployments running 0.29.8 or earlier; audit IAM logs and S3 access logs for cross-organization access patterns; restrict backup permissions to minimal-privilege users only. Within 7 days: rotate all S3 access keys and secret keys used by Dokploy; implement S3 bucket policies enforcing IP/endpoint restrictions and MFA delete; enable detailed CloudTrail and S3 access logging with alerting for cross-org access attempts; conduct a forensic audit of backup destinations accessed per organization. Within 30 days: monitor vendor security advisories for patch availability and upgrade to patched version immediately upon release; engage cloud security team to verify tenant isolation post-patch; review and strengthen access control testing in QA process for multi-tenant systems.

Dokploy CVE-2026-72737

EUVD-2026-55685 CRITICAL

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-08-10 GitHub_M

Authentication Bypass Dokploy

9.6

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.6 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

vuln.today AI

9.6 CRITICAL

Network-reachable tRPC call needs only a low-privileged authenticated member (PR:L, AC:L, UI:N); the missing tenant check crosses a security authority so S:C, exposing (C:H) and poisoning (I:H) another org's backups while availability is unaffected (A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 10, 2026 - 18:32 vuln.today

CVE Published

Aug 10, 2026 - 17:47 cve.org

CRITICAL 9.6

DescriptionCVE.org

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.

AnalysisAI

Cross-tenant authorization bypass in Dokploy 0.29.8 and earlier lets an authenticated organization member with backup permissions reach another organization's S3 backup destinations by supplying a client-controlled destinationId that is never checked against their active organization. Because the referenced destination's S3 accessKey and secretAccessKey are materialized on the attacker's service host, the attacker can read a victim tenant's backup objects and redirect or poison backups across tenant boundaries. No public exploit identified at time of analysis, but the flaw is trivially reachable and breaks the core multi-tenant isolation of the platform (CVSS 9.6, scope-changed).

Technical ContextAI

Dokploy is a self-hostable Platform-as-a-Service that manages application deployments and their backups to S3-compatible object storage, organized into isolated organizations (tenants). The vulnerability is a classic CWE-639 Insecure Direct Object Reference (IDOR/BOLA): the tRPC procedures backup.create, backup.update and backup.restoreBackupWithLogs in apps/dokploy/server/api/routers/backup.ts accept a destinationId from the client and load the corresponding destination record without asserting that destination.organizationId equals ctx.session.activeOrganizationId. The credential-handling helper getS3Credentials in packages/server/src/utils/backups/utils.ts then decrypts and materializes the referenced destination's S3 accessKey/secretAccessKey on whatever service host the attacker controls, meaning the missing ownership check directly exposes another tenant's storage credentials and data.

RemediationAI

Upgrade to the fixed release referenced in the vendor advisory GHSA-56qv-89fq-3h2q (https://github.com/Dokploy/dokploy/security/advisories/GHSA-56qv-89fq-3h2q); an exact fixed version number was not provided in the input data, so confirm the patched version directly from that advisory before deploying - patch available per vendor advisory, released version not independently confirmed here. Until patched, compensating controls include isolating tenants onto separate Dokploy instances so no cross-organization destination records exist to reference, and tightly restricting who is granted backup permissions since that role is the sole prerequisite for the attack (trade-off: legitimate members lose self-service backup management). Additionally, rotate S3 accessKey/secretAccessKey credentials for all backup destinations after patching in case they were already exposed, and audit backup destination access and object integrity for signs of cross-tenant reads or poisoning.