CVE-2026-129433: Patch Dokploy's Compose backup command injection
Upgrade Dokploy installations older than 0.31.1 to a supported fixed release. CVE-2026-129433 lets an authenticated organization member inject shell commands through a Compose backup’s serviceName. On standard installations, execution as root inside the Dokploy container and access to its mounted Docker socket can lead to host compromise. Dokploy’s advisory rates the issue Critical.
Scope and disclosure
The advisory identifies versions before 0.31.1 as affected and 0.31.1 as patched. It describes a member with access to a project and an existing organization backup destination, without requiring administrator or owner privileges. The saved value is inserted into a shell command when a backup runs, including scheduled runs. Restricting the dashboard’s public exposure does not remove a malicious job already stored there.
Dokploy published GHSA-j329-jw7j-rxjm on November 12, 2026 at 08:16:28 UTC. The CVE record followed on November 14 at 12:32:52 UTC. VulnCheck, the assigning CNA, supplies CVSS 4.0 9.4 Critical and CVSS 3.1 9.9 Critical. These are different scoring versions for the same vulnerability. The vendor includes a public proof of concept; that does not establish exploitation in the wild.
The patch in PR #5908 shell-quotes the Docker filter values used by getComposeContainerCommand(). It also repairs other backup-command paths. The 0.31.1 release notes include that patch alongside other security fixes, so updating the full release is preferable to copying one changed line.
Update and check stored backup jobs
- Record the running Dokploy version and deployment image or digest. Identify every instance you manage, including installations with limited network access. If a provider supplies a backported fix, obtain explicit confirmation that its build covers CVE-2026-129433; do not judge a backport solely by the upstream version number.
- Prepare a recovery plan and a trusted backup before the upgrade. Dokploy’s backup documentation describes protecting its database and
/etc/dokploy. Avoid triggering unfamiliar stored backup jobs on an affected instance. If compromise is suspected, preserve evidence and use your incident-response backup procedure instead. - Follow the official Updating Dokploy instructions. Use its stable-update procedure or the script attached to the release you selected. Review the selected release’s requirements and the script before running it with administrative privileges. An operating-system package update alone does not replace the Dokploy application image.
- Confirm that the running service uses the fixed release after the update, not merely that an image was downloaded. Review Compose backup service names, schedules and destinations against your intended configuration. Investigate unexplained changes without executing the suspicious values. Keep secrets out of tickets and diagnostic output.
While arranging the upgrade, restrict management access to trusted administrators and pause suspect backup jobs through approved controls. This may interrupt scheduled backups and is temporary containment, not a substitute for the fix. Do not remove the Docker socket mount as an improvised workaround without understanding which deployment functions depend on it.
After patching and reviewing the saved configuration, run a normal backup with known-good settings and verify its result in the intended destination. Check normal application deployment as well. If you find evidence of compromise, isolate the affected host under your response plan and assess rebuilding it and rotating credentials it could access. A version upgrade does not remove an attacker’s persistence or invalidate copied credentials.
Inspect the public CVE metadata from Linux
This example reads only the public CVE record. It does not contact a Dokploy installation or test whether a host is vulnerable. You need Bash, curl and Python 3. Create a scratch directory in a writable working directory and keep the same terminal session for cleanup. Stop if either setup command fails.
advisory_dir=$(mktemp -d ./dokploy-advisory.XXXXXX) &&
cd -- "$advisory_dir"Save this source as inspect-dokploy-record.py:
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
metadata = record["cveMetadata"]
if metadata["cveId"] != "CVE-2026-129433":
raise SystemExit("Expected CVE-2026-129433")
cna = record["containers"]["cna"]
print("CVE:", metadata["cveId"])
print("CNA:", metadata["assignerShortName"])
print("CVE published (UTC):", metadata["datePublished"])
for product in cna["affected"]:
if product["vendor"] == "Dokploy" and product["product"] == "dokploy":
for version in product["versions"]:
if version["status"] == "affected":
print("Affected: before", version["lessThan"])
elif version["status"] == "unaffected":
print("Listed unaffected version:", version["version"])
for metric in cna["metrics"]:
for key in ("cvssV4_0", "cvssV3_1"):
if key in metric:
score = metric[key]
print("CVSS", score["version"], score["baseScore"], score["baseSeverity"])
print("Metadata only; no Dokploy instance was inspected.")Download the record and run the helper:
curl --fail --silent --show-error --max-time 30 \
'https://cveawg.mitre.org/api/cve/CVE-2026-129433' \
--output dokploy-cve.json &&
python3 inspect-dokploy-record.py dokploy-cve.jsonActual output on Debian 13 with Python 3.12.14, November 14, 2026:
CVE: CVE-2026-129433
CNA: VulnCheck
CVE published (UTC): 2026-11-14T12:32:52.619Z
Affected: before 0.31.1
Listed unaffected version: 0.31.1
CVSS 4.0 9.4 CRITICAL
CVSS 3.1 9.9 CRITICAL
Metadata only; no Dokploy instance was inspected.The helper is specific to this record’s structure. Its publication timestamp belongs to the CVE record, not the earlier vendor disclosure. Save the JSON and its retrieval date elsewhere if you need an incident record; the live metadata can change.
From the scratch directory in the same terminal session, this optional cleanup removes only the two example files and their empty directory:
rm -- inspect-dokploy-record.py dokploy-cve.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dirSetup and cleanup completed without output. No Dokploy instance, exploit, upgrade or live backup operation was tested for this article.
This post was created with assistance from AI.