CVE
Dokploy local privilege escalation via world-writable config dir
Affects Dokploy 0.31.0 and earlier installed via the one-line installer or the manual-installation docs on shared or multi-user hosts. Single-user hosts are not affected.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Shared or multi-user host; single-user hosts are not affected Dokploy installed via the one-line installer or the manual-installation docs (affected versions <= 0.31.0)
Summary
Dokploy, a free self-hostable Platform as a Service, is affected by a local privilege escalation flaw caused by its installer setting /etc/dokploy to be world-writable. An attacker with a low-privilege local account on the same host can replace root-owned configuration directories so that Dokploy runs their substituted scripts as root.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.31.0 and earlier, the hosted installer and manual installation instructions set /etc/dokploy to mode 0777, allowing a local non-root user on a shared host to replace root-owned schedule or Traefik configuration directories. Dokploy subsequently consumes those paths as trusted configuration and can execute substituted scheduled-task scripts as root, resulting in local privilege escalation.
Who should check
Teams running Dokploy on shared or multi-user hosts, installed via the one-line installer or the manual-installation docs.
“All versions installed via the one-line installer or the manual-installation docs, up to and including the current install.sh”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Shared or multi-user host; single-user hosts are not affected Dokploy installed via the one-line installer or the manual-installation docs (affected versions <= 0.31.0)Workaround: The checked facts give no workaround. Because the issue requires an existing non-root local account, removing unneeded local accounts on the host limits exposure until a fix is available.
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-129315 (Dokploy: Local privilege escalation to root: install.sh makes /etc/dokploy world-writable (0777)), 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-129315 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: through 0.31.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Shared or multi-user host; single-user hosts are not affected (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-qxjv-6cvh-32c6)
- Dokploy installed via the one-line installer or the manual-installation docs (affected versions <= 0.31.0) (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-qxjv-6cvh-32c6)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-129315 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129315 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-qxjv-6cvh-32c6
- https://github.com/Dokploy/website/pull/225
- https://github.com/Dokploy/website/commit/2deedf28233d63275a4f55cdcf944e718a779329
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-129315
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-129315"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
through 0.31.0
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-qxjv-6cvh-32c6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129315 |
| Record | NVD · CVE-2026-129315 |
| Other links 2 | |
| Repository | GitHub · Dokploy/website · Pull request #225 |
| Repository | GitHub · Dokploy/website · Commit 2deedf28 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129315
Is CVE-2026-129315 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?
A local non-root user on a shared Dokploy host can make /etc/dokploy world-writable through install.sh. They can then replace root-owned configuration and scheduled-task directories and run code as root.Source: github.com
Which versions are affected by CVE-2026-129315?
dokploy: through 0.31.0.Source: cve.now feed data
Am I affected, and how do I check?
Dokploy versions up to and including 0.31.0 installed through the one-line installer or the manual-installation docs, including the current install.sh. Readers can check the installed Dokploy version and whether the host has other non-root local accounts, since the issue requires one.Source: github.com
How do I fix CVE-2026-129315?
The checked facts name no fixed version or vendor patch identifiers, so no upgrade target can be given from them. Consult the advisory for the current status of the fix.Source: github.com
What if there's no patch?
The checked facts give no workaround. Because the issue requires an existing non-root local account, removing unneeded local accounts on the host limits exposure until a fix is available.Source: github.com