LiveActive security incident?Get immediate response
CVE Record

CVE-2026-72902: Dokploy: Authenticated RCE via Command Injection in registry.testRegistry / registry.testRegistryById

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy allows an authenticated user to execute arbitrary commands on a local or SSH-connected target server because registry.testRegistry and registry.testRegistryById in apps/dokploy/server/api/routers/registry.ts interpolate the password field into an execAsyncRemote shell command instead of using safeDockerLoginCommand. This issue is fixed in version 0.29.13.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Dokploy versions before 0.29.13 let an authenticated user turn a registry password field into commands executed on the Dokploy host or an SSH-connected server. Successful abuse could expose data, alter systems, or interrupt services. Authentication is required, but the potential impact extends beyond the vulnerable application.

Executive priority

Treat as an urgent remediation for every affected Dokploy deployment, especially instances managing production or SSH-connected servers. Prioritize rapid inventory and upgrade because a low-privileged authenticated user could gain command execution with broad operational impact. There is no supplied evidence of active exploitation, so urgency is driven by severity and reachable impact rather than confirmed attacks.

Technical view

This is CWE-78 command injection in registry.testRegistry and registry.testRegistryById. The vulnerable code interpolates the password into an execAsyncRemote shell command rather than using safeDockerLoginCommand. The CVSS 3.1 score is 9.9 because exploitation is network-accessible, low complexity, requires low privileges, needs no user interaction, and can cross security boundaries.

Likely exposure

Exposure is limited to Dokploy versions earlier than 0.29.13. Risk exists where authenticated users can invoke the affected registry-testing functions and Dokploy can execute commands locally or through SSH connections. Internet accessibility increases opportunity, but authentication remains required. The source bundle does not identify specific default roles, configurations, or deployment prevalence.

Exploitation context

The supplied record does not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires an authenticated account and control of the registry password input. If successful, commands execute on a local or SSH-connected target server, potentially compromising confidentiality, integrity, and availability.

Researcher notes

The vulnerable sink is execAsyncRemote in registry.ts, reached through two registry-testing procedures. The password field is unsafely interpolated into a shell command. The vendor fix uses safeDockerLoginCommand and ships in 0.29.13. The bundle provides no exploit telemetry, affected-role details, or evidence of exploitation in the wild.

Mitigation direction

  • Upgrade Dokploy to version 0.29.13 or later.
  • Until upgraded, restrict Dokploy access to trusted administrators.
  • Review authenticated accounts and revoke unnecessary or suspicious access.
  • Follow the Dokploy advisory and release guidance for deployment-specific precautions.

Validation and detection

  • Confirm every Dokploy instance reports version 0.29.13 or later.
  • Verify deployed code includes the vendor's command-handling fix.
  • Inventory SSH-connected targets reachable from affected Dokploy instances.
  • Review relevant application and system logs for suspicious registry tests or unexpected command execution.
  • Investigate affected credentials and connected servers if compromise indicators appear.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-72902 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2026-72902Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Dokploydokploy< 0.29.13Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.