External risk intelligence

Dokploy OS Command Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-72872

Dokploy is a self-hosted Platform as a Service (PaaS) designed to manage application deployments. Such systems typically function as centralized web-based management portals exposed to internal teams or, in many deployment scenarios, the public internet to facilitate remote infrastructure administration and continuous integration workflows.

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 vulnerability affects Dokploy, a self-hosted Platform as a Service tool, and allows authenticated users with deployment permissions to execute arbitrary commands on the host system. This could enable significant compromise of the infrastructure supporting your applications. The primary concern is confirming whether this technology is in use within your environment.

  • Command execution on host systems.
  • Impacts self-hosted PaaS deployment tools.
  • Confirm relevance and exposure within your environment.

Attack Path

How an attacker could exploit the issue

An attacker with service deployment permissions could exploit this vulnerability by providing specially crafted Bitbucket owner or repository names. These inputs are not properly validated and are used in commands to clone repositories, allowing the attacker to execute arbitrary operating system commands on the Dokploy host or a target server.

  • Member with deployment permissions.
  • Saving Bitbucket provider configuration.
  • Arbitrary command execution on host.

Live Threat

Current exploitation, exposure, and threat context

When supported, a member with service deployment permissions could execute arbitrary operating system commands on the Dokploy host or target server. This could allow unauthorized actions on the affected systems.

  • Arbitrary OS commands on host systems.
  • Unvalidated input in command execution.
  • Compromise of deployed applications.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given Dokploy is a self-hostable PaaS, the platform or infrastructure team responsible for its deployment and maintenance is likely to own this vulnerability. The first practical step is to identify all Dokploy instances, assess their reachability and business criticality, and then determine the accountable owner for remediation.

  • Platform/Infrastructure team owns this.
  • 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 free, self-hostable Platform as a Service (PaaS). Developers use it to manage application deployments, typically by running it as a centralized web-based management portal to handle infrastructure administration and continuous integration workflows.

What does CVE-2026-72872 mean?

This CVE describes a critical OS Command Injection vulnerability, classified as CWE-78. It means the software fails to properly sanitize user input, allowing an attacker to inject and execute their own malicious operating system commands directly on the server hosting Dokploy.

How is this vulnerability triggered?

The flaw is triggered when a user with service deployment permissions saves malicious data in the Bitbucket provider configuration. Input that is not a specially crafted repository or owner name will not trigger the bug; the vulnerability specifically relies on the system passing these unvalidated inputs directly into backend clone commands.

Do I need to worry about this?

If you use Dokploy, you should care. Halo Surface Signal notes that because Dokploy is a PaaS designed for infrastructure management, it is often exposed to internal teams or the public internet, which expands the potential reach for an attacker who already has, or obtains, deployment-level access.

How do I respond to CVE-2026-72872?

Your first step is to locate all instances of Dokploy running in your environment. Once identified, ensure you update to version 0.29.13 or later, which contains the fix. Work with your platform or infrastructure team to confirm these instances are patched and to review account permissions.

References