CVE-2026-72902

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available🟡 PoC Available

Authenticated RCE via Command Injection in registry.testRegistry / registry.testRegistryById · Advisory · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/security/advisories/GHSA-w6r4-f26v-8g36
github_release Patch Available

v0.29.13

Patch available: Dokploy/dokploy v0.29.13

https://github.com/Dokploy/dokploy/releases/tag/v0.29.13
github_pr Patch Available

fix(security): command injection in registry.testRegistry / testRegistryById

Patch available: Dokploy/dokploy v0.29.13 (PR #4875 merged 2026-07-20)

https://github.com/Dokploy/dokploy/pull/4875
github_commit Patch Available

commit d3f522b7a6f5 (Dokploy/dokploy)

Patch available: Dokploy/dokploy v0.29.13 (contains commit d3f522b7a6f5)

https://github.com/Dokploy/dokploy/commit/d3f522b7a6f5100fc0fc0bff5851e48d11d459e2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 04:25 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 09:54 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 15:02 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 15:20 UTCEG score recompute
  8. 2026-08-26 14:47 UTCEPSS rescore
  9. 2026-08-25 16:31 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 17:28 UTCEG score recompute
  12. 2026-08-24 12:35 UTCEG score recompute
  13. 2026-08-23 02:36 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 00:13 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 01:36 UTCEG score recompute
  18. 2026-08-20 22:56 UTCEPSS rescore
  19. 2026-08-19 18:43 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 15:37 UTCEG score recompute
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-17 16:43 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 17 more
  1. 2026-08-16 17:52 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:47 UTCEG score recompute
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 04:11 UTCEG score recompute
  7. 2026-08-15 01:31 UTCEPSS rescore
  8. 2026-08-13 22:00 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 23:22 UTCEG score recompute
  11. 2026-08-12 22:21 UTCEG score recompute
  12. 2026-08-12 13:57 UTCEG score recompute
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-11 15:20 UTCEG score recompute
  15. 2026-08-10 20:29 UTCEG score recompute
  16. 2026-08-10 20:05 UTCEG score recompute
  17. 2026-08-10 20:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72902?
CVE-2026-72902 is a critical vulnerability published on August 10, 2026. 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…
When was CVE-2026-72902 disclosed?
CVE-2026-72902 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72902 actively exploited?
CVE-2026-72902 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72902?
CVE-2026-72902 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-72902?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72902, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72902

Explore →

Is Your Infrastructure Affected by CVE-2026-72902?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs