Quick answers
- Is CVE-2026-86059 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86059 being exploited in the wild.
- How severe is CVE-2026-86059?
- Critical severity, with a CVSS score of 9.6, published 22 September 2026.
- Which products and versions are affected?
- Dokploy before 0.29.13.
- Is there a fix for CVE-2026-86059?
- 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-86059 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86059?
- 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 vulnerability is an authorization bypass (IDOR) in the application.one, github.one, gitlab.one, gitea.one, and bitbucket.one routes that return full provider records containing OAuth tokens, private keys, client secrets, and webhook secrets without checking per-member provider access permissions or applying access control filters. An authenticated organization member with read access to applications can bypass hasGitProviderAccess checks to retrieve and abuse exposed credentials. The fix excludes sensitive columns at the database query level in findApplicationById and related procedures.
Affected products
- Dokploy Dokploy before 0.29.13
Timeline
- 2026-09-22: disclosed