CVE
Dokploy command injection in Nixpacks build pipeline
Affects Dokploy before 0.31.1 for applications using the Nixpacks build type with a crafted Publish Directory value. Fixed in 0.31.1.
- 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. Build type set to Nixpacks, with Publish Directory set to a crafted value A Nixpacks deployment must be triggered for the value to be run
Summary
Dokploy, a self-hosted platform-as-a-service, is affected. An attacker who has a low-privilege account with access to an application can, over the network, inject operating system commands through the publishDirectory setting of a Nixpacks deployment and run them on the Dokploy host, which can lead to full compromise of the host.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the Nixpacks publishDirectory build setting accepts shell metacharacters and is interpolated into a docker cp command executed through child_process.exec. An authenticated user with access to an application can execute arbitrary commands on the Dokploy host when triggering a Nixpacks deployment, leading to host compromise through the privileged Docker environment. This issue is fixed in version 0.31.1.
Who should check
Teams running Dokploy that let users with application access set build settings and deploy Nixpacks apps. Check the publishDirectory field on Nixpacks applications.
“OS Command Injection via unsanitized publishDirectory in Nixpacks build pipeline”
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
- Severity9.9/10CVSS 9.9
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Build type set to Nixpacks, with Publish Directory set to a crafted value A Nixpacks deployment must be triggered for the value to be runUpgrade 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-129989 (Dokploy: OS Command Injection via unsanitized publishDirectory in Nixpacks build pipeline), 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-129989 (entry last updated 2026-11-18):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Build type set to Nixpacks, with Publish Directory set to a crafted value (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-98j8-6vjr-c3xw)
- A Nixpacks deployment must be triggered for the value to be run (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-98j8-6vjr-c3xw)
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-129989 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129989 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-98j8-6vjr-c3xw
- https://github.com/Dokploy/dokploy/pull/5911
- https://github.com/Dokploy/dokploy/commit/2cd86b2447daba8fefec1272718d40463e18d6a3
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
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-129989
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-129989"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dokploy dokploy
fixed in 0.31.1
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Dokploy/dokploy · Advisory GHSA-98j8-6vjr-c3xw |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129989 |
| Record | NVD · CVE-2026-129989 |
| Other links 3 | |
| Repository | GitHub · Dokploy/dokploy · Pull request #5911 |
| Repository | GitHub · Dokploy/dokploy · Commit 2cd86b24 |
| Repository | GitHub · Dokploy/dokploy · Release v0.31.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129989
Is CVE-2026-129989 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?
Any authenticated user with access to an application can run arbitrary OS commands on the Dokploy host server. The Publish Directory value is inserted directly into a command when a Nixpacks deployment runs. Because Dokploy has access to the Docker socket, this can lead to full host compromise.Source: github.com
Which versions are affected by CVE-2026-129989?
dokploy: before 0.31.1.Source: cve.now feed data
Am I affected, and how do I check?
The issue involves Dokploy with the Build Type set to Nixpacks and the Publish Directory set to a crafted value. The affected product range ends before version 0.31.1. Check the application's Build Type and Publish Directory settings, and the installed Dokploy version.Source: github.com
How do I fix CVE-2026-129989?
Upgrade Dokploy to 0.31.1, the fixed version listed for this vulnerability.Source: github.com