External risk intelligence

Dokploy Hardcoded Secret Allows Unauthenticated Admin Access and Host Command Execution.

CVE advisorySeverity: CRITICAL (CVSS 10.0)

CVE-2026-45631

Dokploy is a self-hosted Platform as a Service (PaaS) designed to be internet-facing for managing deployments and web applications. As a publicly accessible gateway and management interface, it is intended to be reachable from the internet for normal operation.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in Dokploy, a self-hostable Platform as a Service. An unauthenticated attacker could potentially forge verification tokens to gain administrative access and execute commands on the host system, posing a significant risk to systems running affected versions.

  • Unauthenticated access and host command execution possible.
  • Significant risk to systems running affected versions.
  • Confirm relevance and review exposure of Dokploy instances.

Attack Path

How an attacker could exploit the issue

An attacker can exploit Dokploy by sending a specially crafted request to forge an administrative JSON Web Token (JWT). This allows them to bypass authentication and gain unauthorized access to the system, potentially leading to the execution of commands on the host machine through the SSH terminal.

  • Unauthenticated network access required.
  • Forging JWTs bypasses authentication.
  • Command execution on the host.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an unauthenticated attacker could forge JWTs and trigger auto-sign-in as an administrator, potentially leading to command execution on the host system through the SSH terminal.

  • Host system access.
  • Forge JWTs to gain admin access.
  • Execute commands on the host.

Operational Fix

Recommended remediation, mitigation, and detection steps

The self-hosted nature of Dokploy as a Platform as a Service (PaaS) indicates that teams responsible for managing internal platforms, applications, or infrastructure are likely accountable. The initial practical step is to determine the scope of deployment, confirm reachability and criticality, identify the specific asset owners, and then prioritize remediation based on risk.

  • Platform or application owners should take ownership.
  • Verify Dokploy's reachability and criticality.
  • Plan remediation based on verified exposure.

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 provides a management interface that simplifies deploying, monitoring, and scaling web applications and services. Users typically install it on their own servers to act as a centralized control panel for their infrastructure.

What does CWE-798 mean for CVE-2026-45631?

CWE-798 refers to the use of a hardcoded credential. In this vulnerability, Dokploy contains a static, predictable fallback string used for authentication secrets. Because this secret is embedded directly into the software, an attacker who knows or discovers this value can use it to bypass the intended security checks, effectively granting them unauthorized administrative capabilities.

How does an attacker trigger this vulnerability?

An attacker triggers this by submitting a request containing a forged email verification token, which utilizes the hardcoded secret to appear legitimate. This grants them immediate administrator access. Simply accessing the network interface does not trigger the bug; the attacker must specifically craft a malicious authentication request to exploit the flaw.

Is my Dokploy instance at risk?

According to Halo Surface Signal, Dokploy is designed as an internet-facing gateway to manage deployments. If your instance is reachable from the public internet, it is at higher risk because it is directly accessible to external attackers. Instances restricted to private, internal-only networks face a reduced immediate threat profile but should still be secured.

What steps should I take if I use Dokploy?

First, identify your running version to see if it is between 0.27.0 and 0.29.2. If it is, prioritize upgrading to version 0.29.3 or later, which contains the fix for the hardcoded secret. Until you can upgrade, verify the network accessibility of your instance and restrict access to trusted IP addresses where possible to limit potential exposure.

References