Contact us
← CVEHit Business AdvisoryDokploy backup flaw lets members run commands as root — CVE-2026-129433: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

Dokploy backup flaw lets members run commands as root — CVE-2026-129433: Business Triage9.9/10CRITICAL · CVSS 3.1VulnCheckFix availableVersion 0.31.1CISACVE.org sourceNo KEVChecked Nov 16, 2026

Update Dokploy to 0.31.1, then check member access and backup settings. Research: primary sources retrieved 2026-11-16.

Check these three things.

  1. System owner: confirm Dokploy servers run version 0.31.1 or later.
    What to confirm
    • Check every Dokploy server, including test and staging servers.
    • The CVE record and the vendor advisory both list versions before 0.31.1 as affected.
    • The vendor advisory lists 0.31.1 as the patched version.
    • Record these evidence fields:
      • Installed version.
      • Where the version was read.
      • Date it was read.
  2. Security owner: confirm who can sign in to Dokploy servers before 0.31.1 as a member, from any network.
    When the risk applies
    • Exploitation needs an authenticated organization member account. Admin or owner rights are not needed.
    • The member needs access to at least one project. The vendor advisory says a valid backup destination ID is also needed.
    • The injected value runs when a scheduled backup runs. The vendor advisory says the default schedule is every minute.
    • Host takeover also needs the Docker socket mounted into Dokploy. The vendor advisory says standard installations do this.
    • Public exposure of the Dokploy sign-in and API is unknown. A network attack vector does not show that any installation is reachable from the internet.
    • A reachable sign-in page alone proves neither that the server is vulnerable nor that it is safe. The installed version and the member accounts decide that.
    • Records needed:
      • List of member accounts, including shared accounts, automation accounts and former staff.
      • Firewall, reverse proxy or load balancer settings that show who can reach the Dokploy address.
      • Container settings that show whether the Docker socket is mounted into Dokploy.
  3. Operations owner: check Dokploy backup service names and host activity for signs of injected commands.
    What the records can show
    • Stored backup settings:
      • Compose backup entries whose service name contains quotes, semicolons, dollar signs or other shell characters.
      • Backups created or changed by member accounts through backup.create or backup.update.
    • Host records around scheduled backup runs:
      • Unexplained commands run as root in the Dokploy container.
      • New containers or unexpected outbound connections from the Dokploy host.
    • The sources name stored backup service values as the direct sign. The host signs are reasonable places to look, not source-confirmed indicators.
    • Missing logs do not prove nothing happened. An update does not rule out earlier harm.
    • If the records show injected commands, escalate to the Security owner to start incident response now.

Update any Dokploy server before 0.31.1 that has member accounts. Then review its backup settings for injected commands.

Do Now

  • System owner: update affected Dokploy servers to version 0.31.1.
    What to ask
    • The vendor advisory and the CVE record list 0.31.1 as the fixed version. Both list versions before 0.31.1 as affected.
    • Completion evidence for each server:
      • Installed version showing 0.31.1 or later.
      • Where the version was read.
      • Date it was read.
    • The update does not rule out earlier harm. The third check still applies.
  • Security owner: start incident response if backup settings or host records show injected commands.
    What to ask
    • Trigger: a compose backup service name with shell characters, or unexplained root-level activity on the Dokploy host.
    • Scope: list the environment variables, deployment keys and database credentials Dokploy manages. The vendor advisory says these are accessible after exploitation.
    • Completion evidence:
      • Incident record opened.
      • Named owner.
      • Date opened.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

The reported finding

OS command injection through the compose backup serviceName field (CWE-78)

Original advisory →
Required conditions
  • Dokploy before 0.31.1.
  • An authenticated organization member account. The vendor advisory says no admin or owner role is needed.
  • Member access to at least one project and a valid backup destination ID, per the vendor advisory.
  • A scheduled compose backup that runs. The default schedule is every minute.
  • The Docker socket mounted into Dokploy, for host takeover. The vendor advisory says standard installations mount it.
Reported outcome
  • The CVE record says getComposeContainerCommand() places the serviceName value in a shell command. Members can store values with shell metacharacters through the backup.create or backup.update tRPC procedures.
  • Stored values run as root when scheduled backups run. The CVE record reports host takeover through the mounted Docker socket.
  • The vendor advisory reports that the serviceName schema applies no character restriction, while other shell-adjacent fields are validated.
  • The vendor advisory reports that environment variables, deployment keys and database credentials managed by Dokploy become accessible.
  • The sources describe the flaw. They do not report harm to any specific organization.
Ratings
  • VulnCheck, the CVE assigner: CVSS 3.1 score 9.9 Critical and CVSS 4.0 score 9.4 Critical.
  • GitHub advisory GHSA-gfc5-hfj7-fjwc lists the same two scores.
  • The vendor advisory lists severity critical with CVSS 3.1 score 9.9. Its CVSS 4.0 score is empty.
  • CISA ADP SSVC, dated 2026-11-16T18:23:47.234759Z: Exploitation none, Automatable no, Technical Impact total. Exploitation none does not show that no attacks occurred. Automatable no does not show how often attacks happen. Technical Impact total does not show likelihood.
  • No KEV: the CISA KEV catalog (version 2026.11.13), retrieved November 16, contains no entry for this CVE. KEV is separate from the CISA assessment. No KEV does not mean no exploitation.
Terms in plain words
  • OS command injection: the application puts text from a user into a command, and the server runs that text as part of the command.
  • Docker socket: a control channel that lets software start, stop and manage every container on the host. Whoever can use it can usually control the host.
  • tRPC procedures: the named requests that Dokploy's API accepts, such as backup.create.
  • Member: an ordinary organization account, below admin and owner.

Fix guidance

  • Fix available: the vendor advisory lists 0.31.1 as the patched version.
  • Affected range: versions before 0.31.1, per the CVE record and the vendor advisory. The CVE record also lists release notes and a patch commit for 0.31.1.
  • GitHub advisory GHSA-gfc5-hfj7-fjwc repeats the description, but its retrieved text leaves the affected and fixed version fields empty. The CVE record and vendor advisory supply the version facts.
  • An update to 0.31.1 does not rule out earlier harm. Review backup settings and host records for activity before the update.

What IntegrityLab.ai can check

  • Checked scope: current assessor source code only, verified 2026-11-16. No scan, detector run or deployment check was made.
  • The current web-service discovery keeps the URL, host, port, response status, page title, web-server banner and technology indications.
  • An exact read-only search of the current assessor app found no Dokploy entry and no CVE-2026-129433 entry. This does not establish a validated detector for this CVE.
  • The search does not establish absence from a deployed service or from dynamically downloaded templates.
  • A reachable web service does not establish the Dokploy product, the installed version, user permissions, the vulnerability or compromise.

How to read the score

VulnCheck CVSS 3.1: 9.9 (CRITICAL). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

Need an independent review of your public exposure?

See IntegrityLab.ai →

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…