# CVE-2026-128328: Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoDirectories repoPath


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-5jph-mp6v-5c49, GHSA-q7cq-vxv7-449c

## What is CVE-2026-128328?

CVE-2026-128328 is a medium-severity vulnerability in dokploy, published on 13 Nov 2026. 

### Official description

Dokploy 0.28.0 before 0.31.1 contains a path traversal vulnerability that allows authenticated organization members to list tracked files of any git repository by supplying an arbitrary repoPath to patch.readRepoDirectories. Attackers with read access to one service can enumerate file and directory names of other tenants' application and compose source trees on the host or managed servers.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-128328?

1 open source package ship an affected version, including dokploy/dokploy.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dokploy/dokploy` | GitHub | `pkg:github/dokploy/dokploy` | From 0.28.0 | 0.31.1 |

## How do I fix CVE-2026-128328?

Upgrade dokploy/dokploy to 0.31.1 or later.

## Is CVE-2026-128328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128328 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128328 and fix it if it is affected.

What it is: CVE-2026-128328 is a medium-severity vulnerability in dokploy, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128328 exists.

Affected packages and fixed versions:
- dokploy/dokploy (GitHub): affected from 0.28.0; fixed in 0.31.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128328/ (Markdown: https://insights.sbomify.com/CVE-2026-128328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128328
- OSV: https://osv.dev/vulnerability/CVE-2026-128328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128328/
Summaries are generated and may contain mistakes; the official description above is the record.
