CVE-2026-72737 Dokploy CVE debrief

Who should care

Defenders responsible for Dokploy instances, particularly those with multiple organizations and backup data, should assess exposure and prioritize patching to prevent unauthorized access to backup data.

Why it matters

CVE-2026-72737 is a critical vulnerability in Dokploy that allows an authenticated member with backup permissions to access and manipulate backup data across organizations. Defenders should prioritize verifying and patching Dokploy instances to prevent unauthorized access to backup data.

• Potential unauthorized access to backup data across organizations
• Possible manipulation of backup data
• Required verification of Dokploy instance and application of patches
• Need for restricted backup permissions to prevent exploitation

Technical summary

The vulnerability is caused by the lack of verification of the destination organization's ID in the backup.create, backup.update, and backup.restoreBackupWithLogs functions in Dokploy, a free, self-hostable Platform as a Service (PaaS). This allows an authenticated member with backup permissions for a service in one organization to access and manipulate backup data across organizations, potentially leading to unauthorized access to backup data, manipulation of backup data, or redirection and poisoning of backups across tenant boundaries.

Defensive priority

Defenders should prioritize verifying and patching Dokploy instances to prevent unauthorized access to backup data across organizations.

Recommended defensive actions

• Verify Dokploy instance and apply patches to prevent unauthorized access to backup data
• Restrict backup permissions to prevent exploitation
• Monitor backup data for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the lack of verification of the destination organization's ID in the backup.create, backup.update, and backup.restoreBackupWithLogs functions. This allows an attacker to access and manipulate backup data across organizations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.