# CVE-2026-45663: Dokploy: Remote Code Execution via destinationPath in Container File Upload

> An authenticated attacker can execute arbitrary OS commands on the Dokploy host by injecting shell metacharacters into the destinationPath parameter during container file uploads.

- **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:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-9m66-74x3-5mwr

## What is CVE-2026-45663?

CVE-2026-45663 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.1 and earlier, a command injection vulnerability exists in the Docker file upload functionality. When an authenticated user uploads a file to a container, the destinationPath parameter is not properly sanitized and is directly interpolated into a shell command string. By including shell metacharacters such as ; or ", an attacker can escape the intended docker cp command and execute arbitrary OS commands on the Dokploy host.

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

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


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

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

## Is CVE-2026-45663 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45663 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45663 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-45663/ (Markdown: https://insights.sbomify.com/CVE-2026-45663/index.md)
```

## Sources

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

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