Skip to main content
Menu
CVEs

CVE

Dokploy remote code execution in database password handling

Dokploy before 0.31.1 is affected when an authenticated user updates the password of a MySQL, PostgreSQL, MariaDB, MongoDB or Redis database service. Fixed in 0.31.1.

CVE-2026-129987Published Updated Summary written by a model

9.9CriticalCNA
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. Dokploy before 0.31.1 (v0.29.1 and potentially earlier versions are named as vulnerable). An authenticated user updates the password of a MySQL, PostgreSQL, MariaDB, MongoDB or Redis database service.

Summary

Dokploy, a self-hostable Platform as a Service, fails to properly validate database passwords when changing them for MySQL, PostgreSQL, MariaDB, MongoDB, and Redis. An attacker with a low-privilege login can remotely, without any user action, run arbitrary operating system commands with Dokploy's privileges, which are typically root.

Original description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the database password validation used by the MySQL, PostgreSQL, MariaDB, MongoDB, and Redis change-password procedures permits backticks, and the procedures interpolate attacker-controlled passwords into Bash command strings. An authenticated user who can update a database password can trigger command substitution before the database command runs, resulting in arbitrary operating-system command execution with the Dokploy process privileges, which are typically root. This issue is fixed in version 0.31.1.

Who should check

Teams running Dokploy before 0.31.1 that let users change passwords on MySQL, PostgreSQL, MariaDB, MongoDB or Redis database services.

“Dokploy v0.29.1 and potentially earlier versions are vulnerable”

github.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • 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.

    Dokploy before 0.31.1 (v0.29.1 and potentially earlier versions are named as vulnerable). An authenticated user updates the password of a MySQL, PostgreSQL, MariaDB, MongoDB or Redis database service.
  • Upgrade 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-129987 (Dokploy: Authenticated RCE via Database Password Command Substitution), 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-129987 (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):
- Dokploy before 0.31.1 (v0.29.1 and potentially earlier versions are named as vulnerable). (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-9932-qg8x-pr32)
- An authenticated user updates the password of a MySQL, PostgreSQL, MariaDB, MongoDB or Redis database service. (source: https://github.com/Dokploy/dokploy/security/advisories/GHSA-9932-qg8x-pr32)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129987 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129987 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-9932-qg8x-pr32
- https://github.com/Dokploy/dokploy/pull/5910
- https://github.com/Dokploy/dokploy/commit/accc2ffbda3e698bad328cc6e9fe5837a7bafba6
- 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-129987
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-129987"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • Dokploy dokploy

    fixed in 0.31.1

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Dokploy/dokploy · Advisory GHSA-9932-qg8x-pr32
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129987
RecordNVD · CVE-2026-129987
Other links 3
RepositoryGitHub · Dokploy/dokploy · Pull request #5910
RepositoryGitHub · Dokploy/dokploy · Commit accc2ffb
RepositoryGitHub · 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-129987

Is CVE-2026-129987 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?

Dokploy does not safely handle command substitution in a database service password. A user who is logged in can enter a crafted password that makes the host run arbitrary OS commands with the privileges of the Dokploy process, typically root.Source: github.com

Which versions are affected by CVE-2026-129987?

dokploy: before 0.31.1.Source: cve.now feed data

Am I affected, and how do I check?

Versions before 0.31.1 are affected, with v0.29.1 and possibly earlier named as vulnerable. The relevant setup is a MySQL, PostgreSQL, MariaDB, MongoDB or Redis database service managed in Dokploy, where the password is updated. Check the installed Dokploy version against 0.31.1 to see which version is in use.Source: github.com

How do I fix CVE-2026-129987?

Upgrade Dokploy to version 0.31.1 or later. No vendor patch identifiers are given beyond that fixed version.Source: github.com

More CVEs