# CVE-2026-45628: Dokploy: Command Injection via Unescaped Branch Fields in Deployment Pipeline

> Authenticated attackers can execute arbitrary commands on the server by injecting malicious input into deployment branch fields.

- **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:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-3frc-cfh9-ch2c

## What is CVE-2026-45628?

CVE-2026-45628 is a critical command injection vulnerability in dokploy, published on 29 May 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). In 0.29.2 and earlier, Dokploy constructs shell commands using JavaScript template literals and executes them via child_process.exec() (which runs through /bin/sh -c). User-supplied branch names, repository URLs, and Docker credentials are interpolated directly into these commands without escaping. This requires an authenticated user with application create/edit privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-45628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45628 is a critical command injection vulnerability in dokploy, published on 29 May 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-45628 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-45628/ (Markdown: https://insights.sbomify.com/CVE-2026-45628/index.md)
```

## Sources

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

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