# CVE-2026-72878: Dokploy: OS Command Injection in backup/restore pipeline via unescaped user-controlled shell arguments

> An authenticated admin can inject OS commands into backup/restore operations, leading to arbitrary code execution on the host machine.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-p2c7-8j28-c7gq

## What is CVE-2026-72878?

CVE-2026-72878 is a critical command injection vulnerability in dokploy, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-72878?


## How do I fix CVE-2026-72878?

No fix has been published for CVE-2026-72878 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72878 being exploited?

There is no known exploitation of CVE-2026-72878 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72878 and fix it if it is affected.

What it is: CVE-2026-72878 is a critical command injection vulnerability in dokploy, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72878 in the wild and no public exploit code.

Affected product: dokploy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72878/ (Markdown: https://insights.sbomify.com/CVE-2026-72878/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72878
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72878
- OSV: https://osv.dev/vulnerability/CVE-2026-72878

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72878/
Summaries are generated and may contain mistakes; the official description above is the record.