# CVE-2026-127212: Dokploy < 0.31.1 Broken Access Control via readAppMonitoring

> Authenticated users on self-hosted multi-tenant Dokploy can read other organizations' container metrics by supplying arbitrary application names.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-mrhc-9wg2-r7rh, GHSA-vxxh-2cp7-gr59

## What is CVE-2026-127212?

CVE-2026-127212 is a medium-severity missing authorization vulnerability in dokploy, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dokploy before 0.31.1 contains a missing ownership check vulnerability in the readAppMonitoring tRPC procedure that allows authenticated attackers to access container metrics belonging to other organizations by supplying an arbitrary appName. Attackers can query getApplicationStats with any application name, including the fixed "dokploy" control-plane service name, to read CPU, memory, network I/O, and block I/O metrics for containers they do not own on self-hosted multi-tenant instances.

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

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

1 open source package ship an affected version, including dokploy/dokploy.

Only installations with a non-default setting turned on are exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dokploy/dokploy` | GitHub | `pkg:github/dokploy/dokploy` | All versions | 0.31.1 |

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

Upgrade dokploy/dokploy to 0.31.1 or later.

## Is CVE-2026-127212 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127212 is a medium-severity missing authorization vulnerability in dokploy, published on 12 Nov 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-127212 exists.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected packages and fixed versions:
- dokploy/dokploy (GitHub): affected all versions; fixed in 0.31.1

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

## Sources

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

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