External risk intelligence

Dokploy Backup Prefix Command Injection

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-129991

Dokploy is a Platform as a Service (PaaS) intended to be self-hosted and network-accessible to manage deployments and services. As a centralized management platform, it is commonly deployed as an internet-facing or network-accessible administrative interface, making the vulnerability reachable in typical operational environments.

OS Command Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Dokploy, a self-hosted Platform as a Service, could allow an authenticated user to execute arbitrary commands on the host system. This impacts the integrity and availability of services managed through Dokploy, as an attacker could gain root-level control. The issue arises from how backup configurations are handled, potentially leading to significant operational disruption if exploited.

  • Unauthenticated commands executed via backup settings.
  • Critical remote control risk for managed systems.
  • Confirm Dokploy relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker with organizational membership and backup permissions could exploit this vulnerability. By providing specially crafted input in the backup prefix field, they can manipulate commands executed during backup or cleanup operations. This could allow them to run arbitrary commands with root privileges on the Dokploy host or connected remote servers, potentially leading to a full system compromise.

  • Authenticated user, backup permission required.
  • Malicious input in backup prefix field.
  • Arbitrary command execution as root.

Live Threat

Current exploitation, exposure, and threat context

An authenticated organization member with backup permissions could execute arbitrary commands as root on the Dokploy host or a configured remote server. This could occur when backups are manually initiated, run on a schedule, or during retention cleanup, potentially impacting the integrity and availability of the host system and its data.

  • Root command execution on hosts.
  • Backup operations trigger command injection.
  • System compromise and data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners, platform teams, and infrastructure teams are likely responsible for addressing this vulnerability within their self-hosted Dokploy instances. The first practical step is to identify all Dokploy deployments, confirm their network accessibility and business criticality, and then determine the accountable team for remediation planning and execution.

  • Identify affected Dokploy instances and owners.
  • Verify backup configurations and network exposure.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Dokploy?

Dokploy is a self-hosted Platform as a Service (PaaS) designed to simplify deploying and managing applications and databases like PostgreSQL, MySQL, and MongoDB. It acts as a centralized dashboard where developers and administrators configure services, monitor infrastructure, and automate routine tasks such as data backups.

What is the vulnerability in CVE-2026-129991?

This vulnerability is classified as CWE-78, or OS Command Injection. It occurs because the software fails to properly sanitize the backup prefix field before including it in system commands. Because the system does not strip out special shell characters, an attacker can append their own malicious commands, which the server then executes with root-level privileges.

How can an attacker trigger this command injection?

An attacker needs authorized backup permissions within a Dokploy organization to trigger the issue. They exploit it by entering crafted input into the backup prefix field. The bug does not trigger during normal service operations that do not involve backup or cleanup processes; it only activates when a backup task is manually started, runs on a schedule, or executes retention-cleanup commands.

Is my Dokploy instance affected?

According to Halo Surface Signal, Dokploy is typically deployed as an internet-facing or network-accessible management interface. If your instance is reachable over the network and allows users with backup permissions to log in, you should consider the environment at risk. The vulnerability allows an authenticated member to potentially gain full control over the host or connected remote servers.

How do I secure my environment?

The primary response is to update your Dokploy installation to version 0.31.1 or later, which contains the fix for this flaw. Before updating, identify all running instances and confirm which team is responsible for managing them. You should review your current backup configuration settings and ensure that only trusted users hold administrative permissions within the platform.

References