Dokploy: Arbitrary File Write + Remote OS Command Injection via `certificatePath`
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-78.
Summary
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the apiCreateCertificate schema in packages/server/src/db/schema/certificate.ts accepts a client-supplied certificatePath, and packages/server/src/services/certificate.ts joins that value to the certificate root without confinement. An authenticated user with certificate create or delete permission can use certificatePath to write attacker-controlled certificate content outside the intended directory or delete an out-of-root directory. This vulnerability is fixed in 0.29.13.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA dokploy (Dokploy) Fixed in 0.29.13
Timeline
- 2026-10-02 Threatist record created from CVE-2026-72880
References
More Dokploy vulnerabilities
- TI-2026-33375 Dokploy: Pre-Auth Admin Takeover via Hardcoded Authentication Secret CVSS 3.1CRITICAL 10.0
- TI-2025-33717 Dokploy's Preview Deployments are vulnerable to Remote Code Execution CVSS 3.1CRITICAL 9.8
- TI-2026-62972 Dokploy: Authenticated OS Command Injection in patch.readRepoDirectories (repoPath) leads to RCE as root CVSS 3.1CRITICAL 9.9
- TI-2026-58871 Dokploy: Git Provider Credential Exposure via Unprotected .one Endpoints and application.one CVSS 3.1CRITICAL 9.6
- TI-2026-51118 Dokploy: Remote Code Execution via volume-backup CVSS 3.1CRITICAL 9.9
- TI-2026-51110 Improper privilege management in dokploy CVSS 3.1CRITICAL 9.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences