Skip to main content

Dokploy CVE-2026-45791

| EUVDEUVD-2026-60477 MEDIUM
Insufficient Session Expiration (CWE-613)
2026-08-17 GitHub_M
5.9
CVSS 3.1 · Vendor: GitHub_M
Share

Severity by source

Vendor (GitHub_M) PRIMARY
5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI
5.9 MEDIUM

AC:H reflects the required pre-condition of possessing a stolen session token; C:H for full account access; I:N and A:N as the flaw only extends existing session validity.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

3
Source Code Evidence Fetched
Aug 17, 2026 - 22:24 vuln.today
Analysis Generated
Aug 17, 2026 - 22:24 vuln.today
Patch available
Aug 17, 2026 - 22:03 EUVD

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 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. This issue is fixed in version 0.29.6.

AnalysisAI

Session token invalidation failure in Dokploy allows a stolen better-auth.session_token to persist for up to three days after a victim changes their password, providing an attacker with continued authenticated access even after the victim has attempted to remediate a compromised account. All self-hosted Dokploy deployments prior to version 0.29.6 running the unpatched user.update tRPC procedure are affected. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Obtain valid session token via prior compromise
Delivery
Victim detects breach and changes password
Exploit
Session token remains active in better-auth table
Execution
Replay token against Dokploy API
Persist
Access deployment secrets and infrastructure configuration
Impact
Maintain persistent unauthorized access for up to 3 days

Vulnerability AssessmentAI

Exploitation The attacker must possess a valid better-auth.session_token for a target Dokploy account obtained through a prior compromise vector - this vulnerability does not provide initial access. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The NVD CVSS score of 5.9 with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N accurately reflects the bounded real-world risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who has obtained a Dokploy better-auth.session_token through phishing, network interception, or prior host compromise uses that token to authenticate to the Dokploy API. After the victim detects the compromise and changes their password expecting to evict the attacker, the stolen session token continues to authenticate API requests for up to three additional days, allowing the attacker to access deployment configurations, environment variables, and infrastructure credentials managed by the Dokploy instance.
Remediation Upgrade to Dokploy 0.29.6, which modifies the user.update procedure to revoke existing session tokens upon password change. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

CVE-2026-24841 CRITICAL POC
9.9 Jan 28

Dokploy self-hosted PaaS prior to 0.26.6 has a critical command injection vulnerability (CVSS 9.9) allowing authenticate

CVE-2026-24840 HIGH POC
8.0 Jan 28

Dokploy versions before 0.26.6 contain hardcoded database credentials in the installation script, causing nearly all dep

CVE-2026-72901 CRITICAL
9.9 Aug 10

Command injection in Dokploy (self-hosted PaaS) before 0.29.13 lets an authenticated low-privilege member run arbitrary

CVE-2026-45631 CRITICAL
10.0 May 29

Remote code execution in Dokploy 0.27.0 through 0.29.2 allows unauthenticated attackers to forge email-verification JWTs

CVE-2026-72902 CRITICAL
9.9 Aug 10

Command injection in Dokploy (self-hostable PaaS) before 0.29.13 lets an authenticated user run arbitrary OS commands on

CVE-2026-72867 CRITICAL
9.9 Aug 10

Authenticated command injection in Dokploy (self-hostable PaaS) versions 0.29.3 through 0.29.12 lets a low-privileged us

CVE-2026-72862 CRITICAL
9.9 Aug 10

Command injection in Dokploy self-hosted PaaS versions prior to 0.29.13 lets an authenticated user with database-service

CVE-2026-72872 CRITICAL
9.9 Aug 10

OS command injection in Dokploy (self-hosted PaaS) before 0.29.13 lets a low-privileged team member with service-deploym

CVE-2026-72868 CRITICAL
9.9 Aug 10

Command injection in Dokploy self-hosted PaaS before 0.29.13 lets a low-privileged organization member run arbitrary OS

CVE-2026-72882 CRITICAL
9.9 Aug 10

OS command injection in Dokploy (self-hosted PaaS) version 0.28.8 and earlier lets an authenticated user with permission

CVE-2026-72869 CRITICAL
9.9 Aug 10

OS command injection in Dokploy (self-hosted PaaS) before 0.29.13 lets an authenticated user with the backup:restore per

CVE-2026-72865 CRITICAL
9.9 Aug 10

OS command injection in Dokploy self-hosted PaaS prior to 0.29.13 lets an authenticated project member with compose writ

Share

CVE-2026-45791 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy