# CVE-2026-72734: Missing authorization in dokploy

> An authenticated user can delete another organization's server registration and retrieve its SSH key due to missing authorization checks.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **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:** 11 Aug 2026
- **Also known as:** GHSA-3rpx-c3j9-q99x

## What is CVE-2026-72734?

CVE-2026-72734 is a high-severity missing authorization 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.28.7 until 0.29.13, the server.remove tRPC mutation in apps/dokploy/server/api/routers/server.ts accepts a caller-controlled serverId and calls haveActiveServices, findServerById, removeDeploymentsByServerId, and deleteServer without verifying that currentServer.organizationId equals ctx.session.activeOrganizationId. An authenticated owner or administrator with server:delete in one organization who previously observed another organization's serverId can delete that organization's server registration and deployment records, interrupt Dokploy management, and receive the associated plaintext SSH private key even though server.one denies the same cross-organization read. This issue is fixed in version 0.29.13.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-72734 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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