External risk intelligence

Dokploy WebSocket Handler Authorization Bypass Leads to Host Compromise

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-129316

Dokploy is a self-hosted Platform as a Service (PaaS) solution. PaaS products are commonly deployed as internet-facing management portals or gateways to facilitate remote application deployment and monitoring, making the web-based administrative interface and its associated WebSocket handlers typically accessible over the network.

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 in the Dokploy platform could allow unauthorized access to unrelated containers, sensitive logs, and host systems. This issue arises from how the platform handles service identification within its Docker terminal, container log, and monitoring features. The primary concern is confirming if Dokploy is used and if it is exposed to potential threats.

  • Unauthorized access to container and host systems.
  • Confirms Dokploy relevance and exposure.
  • Assess Dokploy use and network exposure.

Attack Path

How an attacker could exploit the issue

An attacker with read access to any service in Dokploy could exploit this vulnerability by targeting unrelated containers. This could lead to obtaining a root shell within the Dokploy panel container, enabling access to other tenants' sensitive data and potentially compromising the entire host system through the mounted Docker socket.

  • Requires read access to any service.
  • Targets unrelated container via WebSocket handlers.
  • Leads to host compromise and data access.

Live Threat

Current exploitation, exposure, and threat context

A low-privileged user with read access to any service could potentially gain root access to the Dokploy panel container. This access could allow them to read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host system.

  • Host system and tenant data at risk.
  • Unauthorized access to container and host systems.
  • Complete system compromise and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for Dokploy, the self-hosted PaaS, should prioritize identifying all instances of the software, assessing their network exposure, and confirming business criticality. The first practical move is to locate all deployments, determine their reachability and importance, identify the accountable owner, and then plan remediation efforts based on the identified risks.

  • Identify Dokploy deployments and owners.
  • Verify network exposure and criticality.
  • Plan remediation based on 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 Platform as a Service (PaaS) designed to simplify application deployment and management. It allows developers to manage containers, logs, and monitoring through a centralized web-based dashboard. Because it functions as an administrative gateway for infrastructure, it is often deployed to provide remote access to application environments.

What is the vulnerability in CVE-2026-129316?

This vulnerability is classified as CWE-862, which is a Missing Authorization error. In affected versions of Dokploy, the system fails to properly verify if a user has permission to access specific resources when interacting with certain WebSocket handlers. This allows a user to bypass intended restrictions and interact with containers or services they are not authorized to view or manage.

How does an attacker trigger this issue?

An attacker needs existing read access to at least one service within the Dokploy platform to trigger the flaw. By sending specifically crafted requests to the Docker terminal, container-log, or monitoring WebSocket handlers, they can manipulate the serviceId to target unauthorized containers. The bug is not triggered by users lacking any authenticated access, as the mechanism requires an established session to exploit the handler logic.

Is my deployment at risk?

According to Halo Surface Signal, this vulnerability is particularly relevant for Dokploy instances that are internet-facing. Because PaaS solutions are commonly deployed as accessible management portals, the risk is higher if the administrative interface is reachable over the network. If your instance is internal and restricted, the attack surface is smaller, though you should still verify your configuration.

How should I respond if I use Dokploy?

Your first step is to identify all Dokploy deployments in your environment and confirm their current versions. Since this issue is resolved in version 0.31.0, you should plan to update to that version or later as soon as possible. Additionally, verify which users have read access to your services, as restricting access can serve as a temporary mitigating control until you can complete the upgrade.

References