Quick answers
- Is CVE-2026-72734 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72734 being exploited in the wild.
- How severe is CVE-2026-72734?
- High severity, with a CVSS score of 8.4, published 10 August 2026.
- Which products and versions are affected?
- Dokploy 0.28.7 to 0.29.12.
- Is there a fix for CVE-2026-72734?
- A patch was published on 2026-07-20: Fix merged in commit 4aee66b Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72734 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72734?
- Check whether you run Dokploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The server.remove tRPC mutation in Dokploy accepts a caller-supplied serverId and executes deletion operations (haveActiveServices, findServerById, removeDeploymentsByServerId, deleteServer) without verifying that the target server's organizationId matches the authenticated user's activeOrganizationId. This is an insecure direct object reference (IDOR) / broken authorization flaw. An authenticated user (owner or administrator with server:delete permission) in Organization A who has previously observed a serverId from Organization B can invoke server.remove with that serverId to delete the entire server registration and deployment records, interrupt management operations, and extract plaintext SSH private keys—actions that server.one correctly denies via authorization checks. The vulnerability requires authentication and prior knowledge of a valid serverId from another organization, but affects confidentiality, integrity, and availability. Fixed in version 0.29.13.
Affected products
- Dokploy Dokploy 0.28.7 to 0.29.12
Timeline
- 2026-08-10: disclosed
- 2026-07-20: patched: Fix merged in commit 4aee66b