CVE-2026-72879

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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
Elevated
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.4Exploit: Elevated riskExposed: 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.8, the getRegistryCommands() function in packages/server/src/utils/cluster/upload.ts interpolates registry.password and registry.registryUrl directly into a shell command without escaping. An authenticated user with project access can configure malicious registry credentials and trigger a swarm deployment to execute arbitrary OS commands on the Dokploy server, read or modify host files, and access other containers through Docker. This issue is fixed in version 0.29.8.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
58(Track*)
EG Risk 58/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
Severity94% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

Advisory Details (4)

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

Command Injection via Registry Credentials in Swarm Upload · Advisory · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/security/advisories/GHSA-prwq-2mcm-mvhr
github_release Patch Available

v0.29.8

Patch available: Dokploy/dokploy v0.29.8

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

fix: prevent registry password from appearing in error messages and shell commands

Patch available: Dokploy/dokploy v0.29.8 (PR #4579 merged 2026-06-08)

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

commit 1f4f94042f1d (Dokploy/dokploy)

Patch available: Dokploy/dokploy v0.29.8 (contains commit 1f4f94042f1d)

https://github.com/Dokploy/dokploy/commit/1f4f94042f1d874349c42d8ae7fee51346cd086e

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 41× 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:55 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 15:00 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 15:12 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:29 UTCEG score recompute
  13. 2026-08-23 02:18 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 00:03 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 01:32 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:17 UTCEG score recompute
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-17 15:10 UTCEG score recompute
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 16 more
  1. 2026-08-16 16:40 UTCEG score recompute
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 05:21 UTCEG score recompute
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 02:23 UTCEG score recompute
  7. 2026-08-15 01:31 UTCEPSS rescore
  8. 2026-08-14 00:10 UTCEG score recompute
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 14:06 UTCEG score recompute
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-11 15:37 UTCEG score recompute
  13. 2026-08-11 14:58 UTCEG score recompute
  14. 2026-08-10 20:29 UTCEG score recompute
  15. 2026-08-10 19:20 UTCEG score recompute
  16. 2026-08-10 19:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72879?
CVE-2026-72879 is a critical vulnerability published on August 10, 2026. Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.8, the getRegistryCommands() function in packages/server/src/utils/cluster/upload.ts interpolates registry.password and registry.registryUrl directly into a shell command without escaping. An authenticated user with…
When was CVE-2026-72879 disclosed?
CVE-2026-72879 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72879 actively exploited?
CVE-2026-72879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.2% of all scored CVEs.
What is the CVSS score of CVE-2026-72879?
CVE-2026-72879 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-72879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72879, 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-72879

Explore →

Is Your Infrastructure Affected by CVE-2026-72879?

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