# CVE-2026-72872: Dokploy: OS Command Injection via Bitbucket `owner`/`repository` in `git clone`

> An attacker with deployment permissions can execute arbitrary OS commands on the host by injecting malicious input into Bitbucket repository fields.

- **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-grrj-6xrh-j6vp

## What is CVE-2026-72872?

CVE-2026-72872 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, application.saveBitbucketProvider stores bitbucketOwner and bitbucketRepository without validation and cloneBitbucketRepository in packages/server/src/utils/providers/bitbucket.ts interpolates those values into git clone commands executed through execAsync or execAsyncRemote, allowing a member with service deployment permission to execute arbitrary operating system commands on the Dokploy host or target server. This issue is fixed in version 0.29.13.

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

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


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

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

## Is CVE-2026-72872 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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