Quick answers
- Is CVE-2026-45791 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45791 being exploited in the wild.
- How severe is CVE-2026-45791?
- Medium severity, with a CVSS score of 5.9, published 17 August 2026.
- Which products and versions are affected?
- Dokploy prior to 0.29.6.
- Is there a fix for CVE-2026-45791?
- A patch was published on 2026-05-22: Fix included in v0.29.5 release Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45791 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45791?
- 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 exists in the user.update procedure in apps/dokploy/server/api/routers/user.ts. When a user updates their password, the implementation updates the password field but does not delete existing session tokens from the better-auth.session_token table. This allows previously-issued session tokens to remain valid for up to three days after password change. An attacker with a compromised session token can exploit this by continuing to use the stale token to access the account and perform actions with the user's privileges. The fix implemented in version 0.29.6 adds session cleanup logic to delete old sessions upon password update, ensuring only the current session remains active.
Affected products
- Dokploy Dokploy prior to 0.29.6
Timeline
- 2026-08-17: disclosed
- 2026-05-22: patched: Fix included in v0.29.5 release