CVE-2026-86059

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.5% (41st 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

Also known asEUVD-2026-84544 (ENISA EUVD)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate 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.5%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy organization members without Git provider access can retrieve plaintext provider credentials through github.one, gitlab.one, gitea.one, and bitbucket.one because those protected procedures return full provider rows without applying getAccessibleGitProviderIds or an organization check. The application.one route also returns nested GitHub, GitLab, Gitea, and Bitbucket relations from findApplicationById with GitHub App private keys, OAuth tokens, client secrets, webhook secrets, and app passwords even when hasGitProviderAccess is false. A member with application read access or a provider identifier can therefore bypass per-member provider assignment and use the exposed credentials to access private repositories or manipulate external workflows. This issue is fixed in version 0.29.13.

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Git Provider Credential Exposure via Unprotected .one Endpoints and application.one · Advisory · Dokploy/dokploy · GitHub

https://github.com/Dokploy/dokploy/security/advisories/GHSA-wx75-vxph-2m2f
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 pull request Patch Available

fix(security): git provider secret disclosure via application.one

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

https://github.com/Dokploy/dokploy/pull/4859
GitHub commit Patch Available

commit ecbaf6060bf6 (Dokploy/dokploy)

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

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 63× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86059?
CVE-2026-86059 is a critical-severity vulnerability; its CVE record was published on September 22, 2026. Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy organization members without Git provider access can retrieve plaintext provider credentials through github.one, gitlab.one, gitea.one, and bitbucket.one because those protected procedures return full provider…
When was the CVE record for CVE-2026-86059 published?
The CVE record for CVE-2026-86059 was published on September 22, 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-86059 actively exploited?
CVE-2026-86059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86059?
CVE-2026-86059 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-86059?
A fix for CVE-2026-86059 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86059?

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

Book a Demo →Browse All CVEs