PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-72876 Dokploy CVE debrief

CVE-2026-72876 Dokploy Vulnerability Debrief. Dokploy is a free, self-hostable Platform as a Service (PaaS) with a critical vulnerability allowing arbitrary command execution on another tenant's server. The issue is fixed in version 0.29.13. Administrators and users of Dokploy instances should assess exposure and apply the patch. The vulnerability is caused by a lack of activeOrganizationId ownership checks in swarm.getNodes, swarm.getNodeInfo, swarm.getNodeApps, and swarm.getAppInfos, and nodeId interpolation in execAsyncRemote.

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 instances should assess exposure and apply the patch in version 0.29.13. Operators, platform administrators, and security teams need to review affected scope, apply patches, and verify compensating controls. Vulnerability management and security teams should prioritize patching and verify ownership checks and nodeId interpolation.

Why it matters

CVE-2026-72876 is a critical vulnerability in Dokploy that allows for arbitrary command execution on another tenant's server. Defenders should prioritize patching to version 0.29.13 and verify ownership checks and nodeId interpolation.

  • Potential for unauthorized command execution on another tenant's server
  • Elevation of privileges for callers with server:read permission
  • Lateral movement and access to sensitive data

Technical summary

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, swarm.getNodes, swarm.getNodeInfo, swarm.getNodeApps, and swarm.getAppInfos in apps/dokploy/server/api/routers/swarm.ts accept another organization’s serverId without an activeOrganizationId ownership check, and getNodeInfo in packages/server/src/services/docker.ts interpolates nodeId into execAsyncRemote, allowing a caller with server:read permission to execute arbitrary commands as the configured SSH user on another tenant’s server.

Defensive priority

High

Recommended defensive actions

  • Review and apply the patch in version 0.29.13
  • Verify activeOrganizationId ownership checks in swarm.getNodes, swarm.getNodeInfo, swarm.getNodeApps, and swarm.getAppInfos
  • Validate and restrict nodeId interpolation in execAsyncRemote
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the Dokploy vulnerability. The issue is fixed in version 0.29.13. Evidence is limited to public CVE and NVD records. Defenders should verify affected scope, apply patches, and review compensating controls. Official CVE Program record and NIST NVD detail page provide source-provided CVE metadata and vulnerability assessment.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-72876 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-72876 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.