CVE-2026-45791 Dokploy CVE debrief

Who should care

Dokploy administrators and users who manage user accounts and sessions within the Dokploy platform should assess exposure and verify if their instances are affected by this vulnerability.

Why it matters

CVE-2026-45791 allows a compromised session token to remain valid for up to three days after a password change in Dokploy instances prior to version 0.29.6. Dokploy administrators should verify and update their instances to prevent prolonged session token validity.

• Prolonged session token validity after password changes could allow attackers to maintain unauthorized access
• Compromised session tokens may remain active for up to three days after a password change
• Verification of Dokploy instance updates and session token invalidation procedures is necessary
• Monitoring for unusual activity related to Dokploy instances is recommended

Technical summary

Dokploy's user.update procedure in apps/dokploy/server/api/routers/user.ts updates account.password without deleting other rows from session, allowing a compromised better-auth.session_token session to remain valid for up to three days after a password change. This issue is fixed in version 0.29.6. The vulnerability allows a compromised session token to remain valid for up to three days after a password change in Dokploy instances prior to version 0.29.6. Dokploy administrators should verify and update their instances to prevent prolonged session token validity. The CVE record and NVD entry provide details on the Dokploy vulnerability.

Defensive priority

Verify and update Dokploy instances to prevent prolonged session token validity after password changes

Recommended defensive actions

• Update Dokploy to version 0.29.6 or later
• Review and invalidate existing session tokens after password changes
• Monitor for unusual activity related to Dokploy instances
• Verify Dokploy instance updates and session token invalidation procedures
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the Dokploy vulnerability, but specific exploitation or impact instances are not mentioned. The issue is fixed in version 0.29.6. Dokploy's user.update procedure in apps/dokploy/server/api/routers/user.ts updates account.password without deleting other rows from session, allowing a compromised better-auth.session_token session to remain valid for up to three days after a password change. There are no known instances of exploitation or reported impacts. Defenders should verify Dokploy 0.2

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.