PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72863 Dokploy CVE debrief

CVE-2026-72863 Dokploy WebSocket Authentication Bypass. Dokploy, a free, self-hostable Platform as a Service (PaaS), contains a critical vulnerability in its WebSocket handlers. These handlers authenticate sessions but fail to authorize them, allowing any authenticated member to access any container on the host. This includes the Dokploy container with the Docker socket, potentially leading to root access on the host. The vulnerability is fixed in version 0.29.13. Administrators and users of Dokploy, especially those with multi-tenant environments, should assess exposure and prioritize updating to version 0.29.13 or later.

Vendor
Dokploy
Product
Unknown
CVSS
CRITICAL 9.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-10
Original CVE updated
2026-09-08
Advisory published
2026-08-10
Advisory updated
2026-09-08

Who should care

Administrators and users of Dokploy, especially those with multi-tenant environments, should assess exposure and prioritize updating to version 0.29.13 or later. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified. They should also track exceptions, retest remediated assets, and close the item only after evidence is documented. Additionally, they should review and update Dokploy to version 0.29.13,

Why it matters

CVE-2026-72863 is a critical vulnerability in Dokploy that allows authenticated users to bypass authorization and access any container on the host. Defenders should prioritize updating to version 0.29.13 or later and monitor for suspicious activity.

  • Potential for lateral movement within multi-tenant environments
  • Risk of unauthorized access to sensitive data
  • Possible escalation to root access on the host
  • Need for verification of current exposure and remediation

Technical summary

Dokploy's WebSocket handlers authenticate sessions but do not authorize them, allowing any authenticated member to access any container on the host, including the Dokploy container with the Docker socket. This could lead to root access on the host. The vulnerability is fixed in version 0.29.13. Defenders should prioritize updating to version 0.29.13 or later and monitor for suspicious activity. The CVE record and NVD entry provide details on the vulnerability, emphasizing the need for verification of current exposure and remediation.

Defensive priority

High

Recommended defensive actions

  • Review and update Dokploy to version 0.29.13 or later
  • Restrict access to Dokploy's WebSocket handlers
  • Monitor for suspicious activity on Dokploy containers
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. The Dokploy WebSocket handlers do not authorize sessions after authentication, allowing any authenticated member to access any container on the host.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72863 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-72863

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-72863 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72863

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.