Skip to main content
CVE-2026-133520VulnerabilityPublished

Dokploy 0.28.0 before 0.31.1 contains a path traversal vulnerability in the patch.readRepoDirectories tRPC procedure

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133520· Medium 5.3

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

Data as of 20 Nov 2026, 04:36 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.15.0
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:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 19 Nov 2026.

What to do

Upgrade dokploy to 0.31.1.

Affected software

ProductAffectedFixed in
DokploydokployAffected
  • >=0.28.0 <0.31.1
Fixed in
  • 0.31.1
npmdokploypkg:npm/dokployOther threatsAffected
  • >=0.28.0 <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

A fixed version is available starting from Dokploy 0.31.1. Users should upgrade to version 0.31.1 or later to remediate this vulnerability. No other mitigation or workaround is indicated in the provided data.

Description

Dokploy versions from 0.28.0 up to but not including 0.31.1 contain a path traversal vulnerability in the patch.readRepoDirectories tRPC procedure. This flaw allows authenticated organization members with service read permission to supply a crafted repository path, enabling them to list tracked files of arbitrary git repositories, potentially including those of other organizations. The vulnerability arises because the crafted path is passed unconfined to the git ls-tree command, allowing unauthorized enumeration of source trees.

References

Community reviews

Loading reviews…