External risk intelligence

Dokploy Nixpacks Command Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-129989

Dokploy is a self-hostable Platform as a Service (PaaS) designed to manage application deployments. Such systems typically provide web-based management interfaces that are frequently exposed to the internet to allow remote administration and CI/CD operations, making the platform's management surface a likely target for network-based access.

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 the Dokploy platform, a self-hosted service for deploying applications. An authenticated user with application access could potentially execute arbitrary commands on the Dokploy host by triggering a deployment, leading to a compromise of the host system through its privileged Docker environment.

  • Authenticated users can run commands on the host.
  • Affects self-hosted application deployment platforms.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access to an application within Dokploy can trigger a vulnerability by initiating a Nixpacks deployment. This action exploits a flaw in how the `publishDirectory` build setting handles shell metacharacters, allowing them to be interpreted and executed as commands within the Docker environment. If successful, this could lead to complete compromise of the Dokploy host system.

  • Requires authenticated application access.
  • Triggered during Nixpacks deployment.
  • Results in host system compromise.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user could execute arbitrary commands on the Dokploy host by triggering a deployment, leading to potential compromise through the privileged Docker environment. This may affect the integrity and availability of the host system.

  • Host system data and services.
  • Authenticated user triggers Nixpacks deployment.
  • Host compromise via Docker.

Operational Fix

Recommended remediation, mitigation, and detection steps

The vulnerability in Dokploy's Nixpacks build setting requires attention from teams managing the PaaS infrastructure and application deployments. The immediate first step is to locate all instances of Dokploy, determine their exposure and criticality, and identify the accountable system owners before planning remediation.

  • Infrastructure and platform teams own resolution.
  • Verify Dokploy instance exposure and criticality.
  • Plan remediation based on risk and owner input.

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-hosted Platform as a Service (PaaS). Developers use it to simplify application deployment and management, often functioning as an alternative to proprietary cloud services. Because it automates complex tasks like container orchestration and builds, it requires deep integration with the underlying host operating system to manage Docker environments effectively.

How does CVE-2026-129989 affect Dokploy?

This vulnerability is an instance of CWE-78, or OS Command Injection. It occurs because the system improperly filters input in the 'publishDirectory' build setting. When a user triggers a Nixpacks deployment, the software takes this input and incorrectly treats shell metacharacters as executable commands. This allows an attacker to manipulate the command structure and run unauthorized instructions directly on the host system.

Does any deployment trigger this vulnerability?

No. The flaw is specifically tied to the Nixpacks build configuration. It requires an attacker to be authenticated and have specific access to an application where they can modify or influence the 'publishDirectory' setting. Deployments that do not utilize this specific configuration path or users who lack sufficient application-level permissions cannot trigger this command execution flaw.

Why is this CVE considered relevant to my infrastructure?

Halo Surface Signal indicates this is a likely target because Dokploy is a PaaS designed for remote administration and CI/CD, meaning its management interface is often exposed to the internet. If your Dokploy instance is reachable from outside your private network, an attacker with valid application credentials could potentially move beyond the application layer to compromise the entire host system, rather than just the specific application being deployed.

How do I secure my Dokploy environment?

The primary resolution is to upgrade your Dokploy installation to version 0.31.1 or later, which includes the necessary input validation fixes. Before applying the update, identify all internal instances of the platform and determine which are network-accessible. Once identified, coordinate with the infrastructure teams responsible for your deployment pipeline to ensure the patch is applied systematically across all affected environments.

References