# CVE-2026-72867: Command injection in dokploy

> A low-privileged user can execute arbitrary host commands via unvalidated branch fields in the compose deployment pipeline.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 13 Aug 2026
- **Also known as:** GHSA-cg8g-x23v-5fw8

## What is CVE-2026-72867?

CVE-2026-72867 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). From 0.29.3 until 0.29.13, the incomplete fix for CVE-2026-45628 leaves packages/server/src/db/schema/compose.ts branch fields without server-side validation, allowing a direct compose.update request to store a malicious customGitBranch, branch, gitlabBranch, bitbucketBranch, or giteaBranch. A low-privileged authenticated user can trigger compose.deploy, which passes the stored branch to shell-based Git clone commands in packages/server/src/utils/providers/git.ts, github.ts, gitlab.ts, bitbucket.ts, and gitea.ts, resulting in arbitrary host command execution. This issue is fixed in version 0.29.13.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-602 (Client-Side Enforcement of Server-Side Security), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-72867 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72867 exists.

Public exploit code:

- Working, stdlib-only PoC. A low-privileged authenticated user stores a shell palistener (github_poc): https://github.com/Lulztigre/CVE-2026-72867
- Dokploy <=0.29.12 compose branch stored command injection (CVSS 9.9 Critical) — clean-room exploit, swarm lab orchestration, reproduced live against v0.29.12 with host-takeover channel proof (github_poc): https://github.com/WoYinDao/CVE-2026-72867-CVSS-9.9-Critical
- Dokploy <= 0.29.12 - Authenticated RCE via Command Injection (nuclei): http/cves/2026/CVE-2026-72867.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72867 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72867 exists.

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-72867/ (Markdown: https://insights.sbomify.com/CVE-2026-72867/index.md)
```

## Sources

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

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