Quick answers
- Is CVE-2026-43917 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43917 being exploited in the wild.
- How severe is CVE-2026-43917?
- Informational severity, with a CVSS score of 5.3, published 29 May 2026.
- Which products and versions are affected?
- Dokploy <= 0.19.0.
- Is there a fix for CVE-2026-43917?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-43917 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-43917?
- 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
Multiple tRPC endpoints in Dokploy suffer from an Insecure Direct Object Reference (IDOR) vulnerability. While the 'protectedProcedure' middleware confirms a user is authenticated, it does not automatically enforce organization-level isolation. Over 25 endpoints (including those for deployments, backups, rollbacks, and cluster management) fail to manually verify that the requested resource ID belongs to the user's 'activeOrganizationId'. An attacker with a valid account in one organization can manipulate resource IDs in API calls to kill processes, delete backups, or retrieve Docker Swarm join tokens belonging to other organizations on the same instance. Affected files include deployment.ts, backup.ts, cluster.ts, and others.
Affected products
- Dokploy Dokploy <= 0.19.0
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published by maintainer
- 2026-05-29: disclosed: CVE published to NVD