Executive brief
Dokploy is a self-hosted platform for deploying and managing applications. When a user changes their password, the system failed to invalidate existing session tokens, allowing an attacker who previously compromised a session token to maintain unauthorized access for up to three days. This could enable account takeover or unauthorized application deployment even after the legitimate user changes their password.
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