CVE
Dokploy arbitrary file read in patch.readRepoFile
Affects Dokploy 0.28.0 before 0.31.1 for authenticated users holding service.read permission on an application or compose service. Fixed in 0.31.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.31.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Dokploy 0.28.0 up to but not including 0.31.1 Attacker holds service read permission on an application or compose service
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.54% · 45th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dokploy 0.28.0 before 0.31.1 contains a path traversal vulnerability that allows authenticated organization members to read arbitrary files by supplying ../ sequences in the filePath of patch.readRepoFile. Attackers with service read permission can read /etc/shadow, SSH private keys, and secret environment files on the Dokploy host or managed remote servers.
Who should check
Teams running Dokploy 0.28.0 through 0.31.0, especially those granting service read permission to organization members
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Dokploy 0.28.0 up to but not including 0.31.1 Attacker holds service read permission on an application or compose serviceUpgrade 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-128329 (Dokploy 0.28.0 before 0.31.1 Path Traversal via patch.readRepoFile), 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-128329 (entry last updated 2026-11-13):
Affected:
- Dokploy dokploy: from 0.28.0, fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Dokploy 0.28.0 up to but not including 0.31.1 (source: https://www.vulncheck.com/advisories/dokploy-0.28.0-before-0.31.1-path-traversal-via-patch-readrepofile)
- Attacker holds service read permission on an application or compose service (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-g6rj-m32j-2mc4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-128329 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128329 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dokploy/dokploy/security/advisories/GHSA-g6rj-m32j-2mc4
- https://github.com/Dokploy/dokploy/commit/4b582856b36a0d037ff43ecbed2026d93f22ecc6
- https://github.com/Dokploy/dokploy/pull/5899
- https://github.com/Dokploy/dokploy/commit/40e818b0e0d8e448e7a30c559ebf4e146e5932ae
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
- https://github.com/Dokploy/dokploy/blob/v0.31.0/packages/server/src/services/patch-repo.ts#L148-L181
- https://www.vulncheck.com/advisories/dokploy-0.28.0-before-0.31.1-path-traversal-via-patch-readrepofile
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-128329
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-128329"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
From 0.28.0 · fixed in 0.31.1
Evidence 9
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 6
- Patch
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128329
Is CVE-2026-128329 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
What does this mean?
An authenticated user with service.read permission on an application or compose service can read any file the Dokploy process can read, typically as root. That includes SSH private keys, /etc/shadow and secret environment files on the Dokploy host or managed remote servers.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-128329?
dokploy: from 0.28.0 before 0.31.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 0.28.0 up to but not including 0.31.1 are affected when a user holds service.read permission on an application or compose service. Check the installed Dokploy version and which accounts hold service.read permission.Source: vulncheck.com, github.com
How do I fix CVE-2026-128329?
Upgrade Dokploy to 0.31.1 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com, github.com