Dokploy path traversal in patch.readRepoDirectories procedure
- Exploited
- No known exploitation
- Fix
- Fixed in 0.31.1
- Who is exposed
- Not reported
Summary
Dokploy is affected by a path traversal flaw in its patch.readRepoDirectories procedure. A logged-in user with low privileges, such as an organization member with service read permission, can reach it remotely and supply a crafted repository path to list the tracked files of other git repositories, including other organizations' application and source trees.
Written by a model
Original description
Dokploy 0.28.0 before 0.31.1 contains a path traversal vulnerability in the patch.readRepoDirectories tRPC procedure that allows authenticated organization members to list tracked files of arbitrary git repositories. Attackers with service read permission can supply a crafted repoPath, which is passed to git ls-tree unconfined, to enumerate other organizations' application and compose source trees.
What to do
Upgrade to a fixed version: 0.31.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133520 (Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoDirectories repoPath), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133520 (entry last updated 2026-11-20):
Affected:
- npm package dokploy: from 0.28.0, fixed in 0.31.1
Fixed versions: 0.31.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133520 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133520 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-q7cq-vxv7-449c
- https://github.com/Dokploy/dokploy/commit/4b582856b36a0d037ff43ecbed2026d93f22ecc6
- https://github.com/Dokploy/dokploy/pull/5899
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
- https://github.com/Dokploy/dokploy/blob/v0.31.0/apps/dokploy/server/api/routers/patch.ts#L181-L202
- https://github.com/Dokploy/dokploy
- https://www.vulncheck.com/advisories/dokploy-0.28.0-before-0.31.1-path-traversal-via-patch-readrepodirectories-repopath
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133520
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133520"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects npm packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-q7cq-vxv7-449c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133520 |
| Record | NVD · CVE-2026-133520 |
| Other links 6 | |
| Patch | GitHub · Dokploy/dokploy · Commit 4b582856 |
| Patch | GitHub · Dokploy/dokploy · Pull request #5899 |
| Repository | GitHub · Dokploy/dokploy · Release v0.31.1 |
| Repository | GitHub · Dokploy/dokploy · apps/dokploy/server/api/routers/patch.ts · L181-L202 |
| Repository | GitHub · Dokploy/dokploy · Repository |
| Link | vulncheck.com · advisories/dokploy-0.28.0-before-0.31.1-path-traversal-via-patch-readrepodirectories-repopath |
Questions about CVE-2026-133520
Is CVE-2026-133520 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133520?
dokploy (npm): from 0.28.0 before 0.31.1.
Source: cve.now feed data
How do I fix CVE-2026-133520?
Upgrade to a fixed version: 0.31.1.
Source: cve.now feed data
Related
- CVE-2026-129989Dokploy: OS Command Injection via unsanitized publishDirectory in Nixpacks build pipeline
- CVE-2026-129986Dokploy: OS Command Injection via filePath in mount.deleteFileMount → HOST RCE
- CVE-2026-129316Dokploy: serviceId lets a member reach any container (Member -> Root) over the docker WebSocket handlers
- CVE-2026-129991Dokploy: Authenticated Command Injection via unescaped backup.prefix in database/service backup commands leads to RCE as root
- CVE-2026-129987Dokploy: Authenticated RCE via Database Password Command Substitution
- CVE-2026-93425Dokploy: Authenticated OS Command Injection in patch.readRepoDirectories (repoPath) leads to RCE as root
No corrections so far. Something wrong on this page? Report an error.