Skip to main content
VulnerabilityPublished

CVE-2026-127212: dokploy · Insecure Direct Object Reference

Affects dokploySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.31.1 when convenient.

Data as of 12 Nov 2026, 22:37 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.14.3
Patch
Available – fixed in 0.31.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade dokploy to 0.31.1.

Affected software

ProductAffectedFixed in
DokploydokployAffected
  • <0.31.1
Fixed in
  • 0.31.1
GitHubdokploypkg:github/dokployOther threatsAffected
  • <0.31.1
Fixed in
  • 0.31.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Dokploy to version 0.31.1 or later, where the missing ownership check vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

Dokploy versions before 0.31.1 have an authorization bypass vulnerability in the readAppMonitoring tRPC procedure. Authenticated attackers can supply arbitrary application names to access container metrics of other organizations on self-hosted multi-tenant instances. This allows unauthorized reading of CPU, memory, network I/O, and block I/O metrics for containers they do not own. The issue is fixed in version 0.31.1.

References

Community reviews

Loading reviews…