OS Command Injection in Dokploy (CVE-2026-72878)
Summary
OS command injection in Dokploy (CVE-2026-72878). Confidential information can be exposed externally. Mitigation: upgrade to 0.29.13 or later.
Original description
The description as published by the source.
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy's backup and restore pipeline constructs shell commands by directly interpolating user-controlled database fields into bash -c "..." and sh -c "..." strings, then executes them via child_process.exec(). An authenticated admin/owner can inject arbitrary OS commands that execute on the host machine running Dokploy (not just inside a container). This vulnerability is fixed in 0.29.13.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-72878 has been found in Dokploy.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade Dokploy to 0.29.13 or later.
If unsure, ask your IT team or search "Dokploy CVE-2026-72878" on the vendor's site.
CVE-2026-72878 (Dokploy) — CWE-78 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.29.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in Dokploy.
Check the vendor advisory for the affected versions of Dokploy.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 0.29.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Dokploy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Dokploy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dokployを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Dokploy to 0.29.13ステージング環境で 0.29.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。