CVE-2026-72737

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

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

Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.8 and earlier, backup.create, backup.update, and backup.restoreBackupWithLogs in apps/dokploy/server/api/routers/backup.ts accept a client-controlled destinationId and use the referenced destination without verifying that destination.organizationId equals ctx.session.activeOrganizationId. An authenticated member with backup permissions for a service in one organization can cause another organization's S3 accessKey and secretAccessKey to be materialized by packages/server/src/utils/backups/utils.ts getS3Credentials on the attacker's service host, read that organization's backup objects, or redirect and poison backups across tenant boundaries.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

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 (value × EchelonGraph’s weight)
Severity96% × 45%
The EG Score, 9.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Cross-organization IDOR in Dokploy backup destinations exposes another tenant's S3 credentials and backups · Advisory · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/security/advisories/GHSA-56qv-89fq-3h2q

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 109 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-10-12 15:41 UTCEG score recompute
  3. 2026-10-11 19:27 UTCEG score recompute
  4. 2026-10-11 16:42 UTCEG score recompute
  5. 2026-10-11 14:02 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  11. 2026-10-06 18:21 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  13. 2026-10-05 18:23 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  15. 2026-10-05 02:35 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  17. 2026-10-04 04:25 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-10-02 22:37 UTCEG score recompute
  20. 2026-10-02 09:18 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-09-30 22:35 UTCEG score recompute
  23. 2026-09-29 05:22 UTCEG score recompute
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  25. 2026-09-27 16:56 UTCEG score recompute
Show 71 more
  1. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-09-27 12:43 UTCEG score recompute
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  4. 2026-09-25 04:01 UTCEG score recompute
  5. 2026-09-23 21:10 UTCEG score recompute
  6. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  7. 2026-09-22 21:16 UTCEG score recompute
  8. 2026-09-21 22:07 UTCEG score recompute
  9. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  10. 2026-09-21 01:56 UTCEG score recompute
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  12. 2026-09-19 17:21 UTCEG score recompute
  13. 2026-09-18 22:14 UTCEG score recompute
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  15. 2026-09-18 00:49 UTCEG score recompute
  16. 2026-09-17 00:44 UTCEG score recompute
  17. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  18. 2026-09-16 06:13 UTCEG score recompute
  19. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  20. 2026-09-15 04:28 UTCEG score recompute
  21. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  22. 2026-09-13 18:06 UTCEG score recompute
  23. 2026-09-12 16:03 UTCEG score recompute
  24. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  25. 2026-09-11 17:52 UTCEG score recompute
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  27. 2026-09-11 14:10 UTCEG score recompute
  28. 2026-09-10 09:56 UTCEG score recompute
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  30. 2026-09-09 05:51 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  32. 2026-09-07 17:16 UTCEG score recompute
  33. 2026-09-06 16:21 UTCEG score recompute
  34. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  35. 2026-09-05 17:50 UTCEG score recompute
  36. 2026-09-04 15:52 UTCEG score recompute
  37. 2026-09-04 08:22 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  39. 2026-09-03 02:30 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  41. 2026-09-01 17:19 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  43. 2026-09-01 07:04 UTCEG score recompute
  44. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  45. 2026-08-30 22:45 UTCEG score recompute
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-08-30 04:18 UTCEG score recompute
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  49. 2026-08-29 09:56 UTCEG score recompute
  50. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  51. 2026-08-26 18:55 UTCEG score recompute
  52. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  53. 2026-08-25 16:20 UTCEG score recompute
  54. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  55. 2026-08-24 14:28 UTCEG score recompute
  56. 2026-08-24 10:45 UTCEG score recompute
  57. 2026-08-23 01:28 UTCEG score recompute
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-22 03:17 UTCEG score recompute
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  61. 2026-08-21 01:21 UTCEG score recompute
  62. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  63. 2026-08-19 18:43 UTCEG score recompute
  64. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  65. 2026-08-18 15:18 UTCEG score recompute
  66. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  67. 2026-08-17 16:49 UTCEG score recompute
  68. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  69. 2026-08-16 18:29 UTCEG score recompute
  70. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  71. 2026-08-16 03:43 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72737?
CVE-2026-72737 is a critical-severity vulnerability; its CVE record was published on August 10, 2026. Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.29.8 and earlier, backup.create, backup.update, and backup.restoreBackupWithLogs in apps/dokploy/server/api/routers/backup.ts accept a client-controlled destinationId and use the referenced destination without verifying that…
When was the CVE record for CVE-2026-72737 published?
The CVE record for CVE-2026-72737 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-72737 actively exploited?
CVE-2026-72737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72737?
CVE-2026-72737 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72737?
No fix for CVE-2026-72737 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72737?

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

Book a Demo →Browse All CVEs