# CVE-2026-45632: Dokploy: Schedule Authorization Bypass Enables Host/Server Command Execution

> Authenticated users can bypass authorization to execute arbitrary commands on the host or remote servers via schedule manipulation.

- **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:** 2 Jun 2026
- **Also known as:** GHSA-7wmr-57mg-h5q6

## What is CVE-2026-45632?

CVE-2026-45632 is a critical missing authorization 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.26.7 and earlier, the schedule router does not enforce organization/role checks. As a result, any authenticated user can create, update, run, or delete schedules belonging to other organizations if they know the scheduleId/serverId. Schedule types server and dokploy-server write and execute scripts on the host or remote servers, enabling RCE on the Dokploy host or a target server.

Weakness: CWE-862 (Missing Authorization), CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-45632 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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