What is the CVSS score of EUVD-2026-55741?

EUVD-2026-55741 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

Which versions of Dokploy are affected by EUVD-2026-55741?

Dokploy versions before 0.29.13 contain a critical remote command execution vulnerability affecting multi-tenant isolation: any authenticated user with minimal server:read permissions can execute…. A patch is available.

How to fix or mitigate EUVD-2026-55741?

Within 24 hours, inventory all Dokploy deployments and determine current versions; flag any instance running pre-0.29.13 for immediate remediation. Within 7 days, apply the vendor-released patch Dokploy 0.29.13 or later to all production and non-production instances. Within 30 days, complete a full audit of authentication logs and system command history for exploitation attempts, verify patch deployment across 100% of instances, and conduct a cross-tenant access control review to confirm isolation is fully restored.

Dokploy EUVD-2026-55741

| CVE-2026-72876 CRITICAL

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

Docker Command Injection Dokploy

9.9

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.9 CRITICAL

Network-reachable endpoint needing only a low-privilege server:read account (PR:L, AC:L); code executes on a different tenant's host so scope changes (S:C) with full RCE giving C/I/A:H.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Aug 10, 2026 - 20:04 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 19:48 vuln.today

Analysis Generated

Aug 10, 2026 - 19:48 vuln.today

CVE Published

Aug 10, 2026 - 19:00 cve.org

CRITICAL 9.9

DescriptionCVE.org

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. This issue is fixed in version 0.29.13.

Articles & Coverage 1

News Critical Cross-Tenant RCE in Dokploy (Docker) Before 0.29.13 - CVE-2026-72876 Aug 11, 2026

AnalysisAI

Cross-tenant remote command execution in Dokploy (self-hosted PaaS) before 0.29.13 lets any authenticated user holding only the server:read permission run arbitrary OS commands on servers belonging to other organizations. The swarm tRPC endpoints never verified that the supplied serverId belonged to the caller's active organization, and getNodeInfo interpolated an attacker-controlled nodeId straight into a remote shell command, chaining a broken multi-tenant authorization flaw with OS command injection. No public exploit or CISA KEV listing has been identified, though the vendor security advisory and a fix-verification test are public.

Technical ContextAI

Dokploy is a free, self-hostable Platform-as-a-Service that manages Docker Swarm clusters across multiple tenant organizations. The affected code lives in the tRPC swarm router (apps/dokploy/server/api/routers/swarm.ts) whose queries swarm.getNodes, swarm.getNodeInfo, swarm.getNodeApps, and swarm.getAppInfos accepted a serverId parameter, and in packages/server/src/services/docker.ts where getNodeInfo built the shell string docker node inspect ${nodeId} --format '{{json .}}' and passed it to execAsyncRemote (an SSH-based remote executor). CWE-78 (OS Command Injection) is the root-cause class: the nodeId was concatenated unsanitized, so shell metacharacters (backticks, $(), ;, |, &&) break out of the intended docker command. The CPE cpe:2.3:a:dokploy:dokploy identifies the single affected application. The fix adds an activeOrganizationId ownership check on each endpoint and wraps nodeId with shell-quote's quote() so it is passed as a single literal token.

RemediationAI

Upgrade to Dokploy 0.29.13 or later, which both adds the missing activeOrganizationId ownership check on the swarm endpoints and shell-quotes the nodeId - this is the primary and complete fix (Vendor-released patch: 0.29.13; see release https://github.com/Dokploy/dokploy/releases/tag/v0.29.13 and advisory GHSA-jj6h-388v-9rwm). If you cannot upgrade immediately, reduce exposure by tightly restricting who holds server:read and any account in shared organizations, and by isolating tenants onto separate Dokploy instances so a cross-organization serverId cannot reference another tenant's host - with the trade-off of higher operational overhead and loss of consolidated management. Additionally, network-segment and firewall the managed servers' SSH access and monitor execAsyncRemote/SSH command activity for anomalous docker node inspect invocations containing shell metacharacters, accepting that this only detects rather than prevents exploitation. Rotate the configured SSH credentials after patching if you suspect prior misuse.