CVE-2026-127212: Dokploy < 0.31.1 Broken Access Control via readAppMonitoring
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.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Dokployto a version that resolves this vulnerability.Fixed in 0.31.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Self-hosted, multi-tenant Dokploy instances running a version before 0.31.1 are exposed. An authenticated user in one organization may be able to read metrics for containers owned by other organizations.
What does an attacker need to exploit it?
The attacker needs an authenticated Dokploy account with low privileges and network access to the instance. They can supply an arbitrary application name to the affected procedure; no user interaction is required.
What information can be disclosed?
The issue exposes container monitoring data, including CPU usage, memory usage, network I/O, and block I/O. The fixed "dokploy" control-plane service name can also be queried.
How can this be remediated?
Upgrade Dokploy to version 0.31.1 or later. The affected versions are those before 0.31.1.