Quick answers
- Is CVE-2026-127212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-127212 being exploited in the wild.
- How severe is CVE-2026-127212?
- Medium severity, with a CVSS score of 4.3, published 13 November 2026.
- Which products and versions are affected?
- Dokploy before 0.31.1.
- Is there a fix for CVE-2026-127212?
- Yes: fixed in 0.31.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-127212 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-127212?
- Check whether you run Dokploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.31.1
Technical details
The readAppMonitoring tRPC procedure validates the caller has monitoring:read role within their organization but does not verify the supplied appName belongs to that organization before passing it to getApplicationStats. An authenticated attacker can query Docker Swarm metrics for any application by name, including the fixed "dokploy" control-plane service, bypassing the tenant isolation mechanism. The vulnerability is limited to self-hosted instances; cloud deployments are protected by an IS_CLOUD guard.
Affected products
- Dokploy Dokploy before 0.31.1
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched