External risk intelligence

Dokploy OS Command Injection Via Compose Backup Service Name.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-129433

Dokploy is a platform designed for managing and deploying applications via Docker. As a self-hosted management interface that provides centralized control over services and deployments, it is typically deployed as a reachable web-based administrative dashboard or API gateway, making its interface commonly accessible to authorized users over the network.

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 vulnerability has been identified in Dokploy that allows authenticated users to execute arbitrary shell commands on the host system by manipulating service names during backup operations. This could potentially lead to a full system takeover when scheduled backups are processed.

  • Authenticated users can run commands as root.
  • This could allow unauthorized host access.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to Dokploy can exploit a vulnerability in the backup procedures by providing specially crafted input for the service name. This input, containing shell metacharacters, is then used in commands executed by the system during scheduled backups. When these backups run, the commands are executed with root privileges, allowing the attacker to potentially compromise the host system by interacting with the mounted Docker socket.

  • Authenticated organization member access required.
  • Service name parameter in backup procedures.
  • Host compromise via root command execution.

Live Threat

Current exploitation, exposure, and threat context

Authenticated organization members could execute arbitrary shell commands on the host system when performing backup operations. This could occur when a user crafts a service name with shell metacharacters, which are then executed as root by scheduled backup jobs.

  • Host system command execution
  • Via crafted service name in backups
  • Complete host takeover

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the Dokploy platform, likely managed by application owners or infrastructure teams. The initial step is to locate all Dokploy instances, verify their network exposure and business criticality, and identify the accountable system owner. Remediation planning should then be prioritized based on these findings.

  • Application owners should address the vulnerability.
  • Verify Dokploy instance reachability and criticality.
  • 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 management platform used to simplify application deployment and service orchestration using Docker. It acts as a centralized administrative dashboard, allowing teams to manage containers, services, and infrastructure deployments through a web interface or API gateway.

What is the vulnerability in CVE-2026-129433?

This vulnerability is an OS command injection, classified as CWE-78. It occurs when an application fails to properly sanitize user-provided input before using it in a system command. In this case, malicious shell metacharacters can be injected into the system, forcing it to execute unauthorized commands.

How does an attacker trigger this command injection?

An attacker must have authenticated access to the Dokploy organization. By using the backup.create or backup.update tRPC procedures, they can save a crafted service name containing shell metacharacters. The bug is triggered when the system runs a scheduled backup, executing those characters as root; simple read-only actions or unauthorized users cannot initiate the flaw.

Is my Dokploy instance at risk?

According to Halo Surface Signal, Dokploy is often deployed as a web-based administrative dashboard or API gateway reachable over the network. If your instance is internet-facing or accessible to unauthorized personnel within your organization, it faces a higher likelihood of being targeted compared to strictly internal, isolated deployments.

What should I do to respond to this threat?

Your first step is to identify all running Dokploy instances across your environment. Once mapped, assess which instances are exposed to the network and determine their business criticality. Coordinate with the accountable system owners to prioritize and plan your remediation efforts, starting with the most exposed or sensitive systems first.

References