CVE
Dokploy command injection in backups enables root code execution
Affects Dokploy before 0.31.1 when a backup on an S3-compatible destination has a prefix set. 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. Backup has a prefix field on an S3-compatible destination Backup type is PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose or web-server Backup runs manually, on its schedule, or through retention cleanup
Summary
Dokploy, a self-hostable Platform as a Service, has a command injection flaw in its backup code, where an unsanitized backup prefix lets an authenticated organization member with backup permission for a service run arbitrary commands as root on the Dokploy host or a configured remote server. The attacker can reach it remotely over the network with a low-privilege account, and the commands run when a PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, or web-server backup runs manually, on schedule, or during retention cleanup.
Original description
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the backup prefix field is only checked for a nonempty value, and normalizeS3Path preserves shell metacharacters before the prefix is interpolated into rclone upload and retention-cleanup command strings. An authenticated organization member with backup permission for a service can execute arbitrary commands as root on the Dokploy host or configured remote server when a PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, or web-server backup runs manually, on schedule, or performs retention cleanup. This issue is fixed in version 0.31.1.
Who should check
Teams running self-hosted Dokploy with backups configured for PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose or web-server services
“identical pattern for every backup type - PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, and the web-server backup”
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.
Backup has a prefix field on an S3-compatible destination Backup type is PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose or web-server Backup runs manually, on its schedule, or through retention cleanupUpgrade 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-129991 (Dokploy: Authenticated Command Injection via unescaped backup.prefix in database/service backup commands leads to RCE as root), 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-129991 (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):
- Backup has a prefix field on an S3-compatible destination (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-2gq3-9q77-8hgv)
- Backup type is PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose or web-server (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-2gq3-9q77-8hgv)
- Backup runs manually, on its schedule, or through retention cleanup (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-2gq3-9q77-8hgv)
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-129991 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129991 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-2gq3-9q77-8hgv
- https://github.com/Dokploy/dokploy/pull/5908
- https://github.com/Dokploy/dokploy/commit/549cdada79a8ddf9bd9d1f153159626d050b4b6a
- 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-129991
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-129991"}.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-2gq3-9q77-8hgv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129991 |
| Record | NVD · CVE-2026-129991 |
| Other links 3 | |
| Repository | GitHub · Dokploy/dokploy · Pull request #5908 |
| Repository | GitHub · Dokploy/dokploy · Commit 549cdada |
| 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-129991
Is CVE-2026-129991 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?
The backup prefix value is placed into shell commands without escaping. An authenticated member can inject arbitrary shell commands that run as root on the Dokploy host or the configured remote server.Source: github.com
Which versions are affected by CVE-2026-129991?
dokploy: before 0.31.1.Source: cve.now feed data
Am I affected, and how do I check?
Dokploy versions before 0.31.1 are in scope where a backup has a prefix field set on an S3-compatible destination. The same pattern applies to PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose and web-server backups. To check, look at the installed Dokploy version and whether any backup's prefix field is set.Source: github.com
How do I fix CVE-2026-129991?
Upgrade Dokploy to version 0.31.1 or later.Source: github.com