A member with backup permission for one service can place shell metacharacters in its backup prefix. When that backup runs, the resulting command can execute as root in the Dokploy container or on a configured remote server.Dokploy lists versions before 0.31.1 as affected and 0.31.1 as patched. The issue covers manual and scheduled backups, plus retention cleanup after a successful backup. The CVE record assigns the flaw CWE-78.
What it allows
How Does CVE-2026-129991 Turn a Backup Prefix Into a Command?
The prefix namespaces backup files in an S3-compatible destination. Dokploy checked only that the value was not empty. Its path normalization trimmed whitespace and slashes, while preserving shell metacharacters. The application then inserted that value into backup upload and retention commands.
According to the advisory, a permitted member can configure a service backup and trigger it manually. A scheduled run can also reach the vulnerable path. Retention cleanup introduces another command path after a successful backup. The member does not need an owner or administrator role when the service grants backup permission.
The advisory describes root execution on the Dokploy host or a configured remote server. Its demonstration specifically verified root execution inside the Dokploy container. Treat host exposure as deployment dependent when assessing the impact. Use the vulnerability intelligence platform to organize the confirmed version and permission facts during remediation.
Who is affected
Which Dokploy Backups Need a CVE-2026-129991 Review?
Review Dokploy deployments running versions before 0.31.1. The advisory names PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose and web-server backups. Focus on services where an organization member can configure backups. Include local and configured remote-server execution paths in the inventory.
Record the running Dokploy version, backup permissions, schedules and configured remote servers. Review existing backup prefixes and recent backup activity for unexpected changes or runs. Logs may support an investigation, but a suspicious prefix alone does not prove execution. The vulnerability management guide helps document patch and verification steps.
Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-129991 from 21 August through 19 November 2026. That measured unit is a discussion post, not an incident or proof of active exploitation. Prioritize the version and permission checks using the vulnerability prioritization framework.
Timeline
-
2026-11-12
Dokploy published GHSA-2gq3-9q77-8hgv and listed 0.31.1 as the patched version.
-
2026-11-18
The CVE record for CVE-2026-129991 was published.
What to do
-
Inventory exposed backup workflows
Identify Dokploy versions, backup-enabled services, member permissions, schedules, backup prefixes and configured remote servers.
-
Upgrade Dokploy
Upgrade affected deployments to 0.31.1 or a later vendor-confirmed fixed release. Include every Dokploy instance that can run these backup types.
-
Verify the running release
After deployment, confirm each running Dokploy instance reports 0.31.1 or a later vendor-confirmed fixed release. Recheck the backup workflows used in that instance.
-
Reduce backup access during rollout
Limit backup configuration and run permissions to trusted members until the upgrade is complete. Review existing prefixes before another backup runs.
-
Investigate unexpected backup activity
Review backup configuration changes and manual or scheduled runs for unusual activity. Correlate with host, container and remote-server logs before concluding that execution occurred.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-129991 in Brandefense Atlas
The Atlas record of CVE-2026-129991: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-129991 require administrator access?
No. The Dokploy advisory says an authenticated member with backup permission for a service can trigger the flaw without an owner or administrator role.
Which Dokploy version fixes CVE-2026-129991?
Dokploy lists 0.31.1 as patched. Upgrade affected installations and verify that each running instance reports 0.31.1 or a later vendor-confirmed fixed release.
Can a scheduled backup trigger the flaw?
Yes. The advisory includes manual runs, scheduled runs and retention cleanup after a successful backup as trigger paths.
Does the vendor demonstration prove host compromise?
The demonstration verified root execution inside the Dokploy container. The advisory also describes command execution on a configured remote server. Assess host impact against the actual deployment.
Sources
- Dokploy backup-prefix command injection advisoryDokploy GitHub Security Advisory
- CVE-2026-129991 recordCVE Program