External risk intelligence

Dokploy Command Injection via File Mounts

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-72882

Dokploy is a self-hostable Platform as a Service (PaaS) designed to manage remote servers and deploy applications. By nature, such administrative and management platforms are commonly deployed as internet-facing web interfaces to facilitate remote service management, making the attack surface reachable from the internet in typical deployments.

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

This advisory details a critical vulnerability in Dokploy, a self-hostable Platform as a Service, that could allow an authenticated user to execute arbitrary commands on a remote server through file mount configurations. The issue, if exploited, could lead to a compromise of the managed server.

  • Injected commands can run on servers.
  • Critical flaw impacts server command execution.
  • Confirm relevance to protect managed infrastructure.

Attack Path

How an attacker could exploit the issue

An attacker with existing access to Dokploy can exploit this vulnerability by creating or updating a file mount for a service. By injecting special characters into the `filePath` field, the attacker can trick Dokploy into running arbitrary commands on the remote server via SSH. This could lead to full control over the managed server if Dokploy is configured in its default deployment model.

  • Authenticated user with file mount access.
  • Injecting shell metacharacters in `filePath`.
  • Remote code execution on managed servers.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user with file mount creation or update privileges could inject shell metacharacters into a file path. This could lead to the execution of attacker-controlled commands on the remote managed server over SSH, potentially resulting in remote code execution from the web interface, especially in default deployment models.

  • Remote managed server access.
  • Attacker-controlled commands via file mounts.
  • Direct remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given Dokploy is a self-hostable PaaS, application owners and platform teams are likely responsible for managing its security. The initial step is to identify all Dokploy instances, confirm their reachability and criticality, and then determine the accountable owner to plan remediation based on risk.

  • Application and platform teams should own.
  • 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 an open-source, self-hosted Platform as a Service (PaaS). It functions as a management layer that simplifies deploying and maintaining applications on remote servers, often acting as a centralized control panel for infrastructure.

What does CVE-2026-72882 mean?

This vulnerability is classified as Improper Neutralization of Special Elements used in an OS Command, or CWE-78. In plain terms, the software fails to properly sanitize input, allowing a user to inject harmful instructions into a system field that the application then executes as a command.

How can an attacker trigger this vulnerability?

An attacker needs an authenticated account with permission to create or update file mounts. The bug is triggered specifically by injecting shell metacharacters into the 'filePath' field; input that does not contain these specific characters will not execute unintended commands.

Is my Dokploy instance at risk?

Halo Surface Signal indicates that Dokploy is frequently deployed as an internet-facing web interface for remote management. Because this setup makes the platform reachable from the internet, any instance accessible outside your internal network faces a higher likelihood of being targeted.

What should I do to secure my Dokploy environment?

Begin by identifying all running Dokploy instances and determining who manages them. Once you have an inventory, verify the network reachability of these servers and prioritize them based on their exposure to the internet while awaiting official updates to address the command injection flaw.

References