An authenticated member must be able to update a database password. The vendor advisory and CNA record list Dokploy versions before 0.31.1 as affected and 0.31.1 as fixed.The flaw can run operating-system commands with the Dokploy process's privileges, which the advisory says are typically root. This is a host-level risk when the required member permission is present. The published CVSS 3.1 score is 9.9 Critical.
What it allows
How Does CVE-2026-129987 Reach the Host?
Dokploy validates a new database password before passing it to a database management procedure. The advisory says its validation permits shell substitution syntax. The procedure then interpolates that password into a Bash command string, so the shell can evaluate the member-controlled value as a command.
The command runs in the Dokploy process context before the intended database operation finishes. The vendor says that process typically has root privileges. A member therefore needs permission to update a database password, but does not need to persuade another user to act.
This database-password path can cause remote code execution on the Dokploy host. Our operational reading is to review password-change permissions first, then investigate unusual use of those permissions. The vulnerability intelligence platform describes how teams can track the affected release and fix.
What Is Known About Exploitation?
The CISA KEV catalog snapshot dated 18 November 2026 does not list CVE-2026-129987. That catalog status does not determine whether a particular host was targeted. The advisory describes a demonstration, not an observed campaign.
Brandefense Blackhole counted one dark-chat post mentioning this CVE from 21 August through 19 November 2026. The measured unit is posts for this identifier, and the count is an internal research signal. It does not establish an incident or active exploitation.
Who is affected
Which Dokploy Versions and Database Services Are Affected?
The GitHub advisory and CNA record mark Dokploy versions before 0.31.1 as affected. The advisory narrative demonstrates version 0.29.1 and says earlier versions may also be affected. Use the stated affected range for inventory; do not treat the demonstrated build as the lower bound.
The affected password-change procedures cover MySQL, PostgreSQL, MariaDB, MongoDB, and Redis services managed through Dokploy. Exposure requires an authenticated member who can update one of those database passwords. A deployment's panel version and its member permissions both matter to this assessment.
How Should Operators Patch and Verify?
Update affected Dokploy panels to 0.31.1 or a later vendor-confirmed release. Prioritize panels where ordinary members can change database passwords. Review member roles while the update rolls out; permission changes can reduce access to the trigger but do not repair the flaw.
After deployment, check the version reported by each running panel and confirm it is at least 0.31.1. Test authorized password changes for the five listed database types used in your environment. Compare recent password-change activity with approved work and investigate unexpected host process activity if logs support it.
Record the version check and role review in the patch management process. These validation and investigation steps are our defensive recommendations drawn from the advisory's access condition. They are not claims that a specific host was compromised.
Timeline
-
2026-11-12
The Dokploy GitHub security advisory was published and listed versions before 0.31.1 as affected.
-
2026-11-18
The GitHub CNA published CVE-2026-129987 with a CVSS 3.1 score of 9.9 and listed 0.31.1 as fixed.
What to do
-
Inventory Dokploy panels and database roles
Record each panel's running version and which authenticated members can change MySQL, PostgreSQL, MariaDB, MongoDB, or Redis passwords.
-
Restrict the trigger during rollout
Review password-change permissions and remove unnecessary member access while scheduling the update. This limits the stated prerequisite but does not fix the code.
-
Install Dokploy 0.31.1 or later
Update affected panels to the vendor's patched release or a later vendor-confirmed version.
-
Verify the running version and behavior
Confirm each panel reports 0.31.1 or later after deployment. Test approved password changes for database services used by the organization.
-
Review unexpected activity
Compare available password-change, authentication, and host process logs with approved changes. Investigate anomalies without assuming they prove this CVE was exploited.
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-129987 in Brandefense Atlas
The Atlas record of CVE-2026-129987: 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-129987 require a Dokploy account?
Yes. The advisory requires an authenticated member with permission to update a database password.
Which database services use the affected password-change path?
The CNA record names MySQL, PostgreSQL, MariaDB, MongoDB, and Redis. Check which of these services each Dokploy panel manages.
Which Dokploy version fixes CVE-2026-129987?
The GitHub advisory and CNA record identify 0.31.1 as the fixed version. Verify the running panel reports 0.31.1 or later after updating.
What privileges can the injected command have?
The advisory says commands run with the Dokploy process's privileges, which are typically root. The actual privilege level depends on the deployment.
Sources
- Dokploy database password command substitution advisoryGitHub Security Advisory
- CVE-2026-129987 recordGitHub CNA via CVE Program
- Known Exploited Vulnerabilities CatalogCISA