Unauthenticated code execution via unchecked preview deployments
Published Jul 14, 2025 · Updated Jul 15, 2025
Missing authorization in Dokploy before 0.24.3 allows remote attackers to execute code through public-repository preview deployments. The GitHub webhook path automatically builds untrusted pull-request code with preview environment variables without first requiring the pull-request author to have collaborator permissions. Exposure requires preview deployments on a public repository; successful exploitation reads configured secrets and runs attacker-controlled code in the deployment environment.
Summary
What happened
Missing authorization in Dokploy before 0.24.3 allows remote attackers to execute code through public-repository preview deployments. The GitHub webhook path automatically builds untrusted pull-request code with preview environment variables without first requiring the pull-request author to have collaborator permissions. Exposure requires preview deployments on a public repository; successful exploitation reads configured secrets and runs attacker-controlled code in the deployment environment.
The record
- CVE
- CVE-2025-53825
- Published
- Jul 14, 2025
- Updated
- Jul 15, 2025
- Vendor
- Dokploy
- Product
- Dokploy
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2025CVE publishedPublication date reported by the CVE source.
- Jul 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.24.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Vendor advisory preview-deployment proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo