A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the internal Dqlite database cluster fails to perform proper TLS client and server authentication. Specifically, the Juju controller's database endpoint does not validate client certificates when a new node attempts to join the cluster. An unauthenticated attacker with network reachability to the Juju controller's Dqlite port can exploit this flaw to join the database cluster. Once joined, the attacker gains full read and write access to the underlying database, allowing for total data compromise.
CVE-2026-4370
“—” beside the score: it is equal to NVD's CVSS score.
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-02. NVD baseline CVSS 10.0; sources differ by 0.0.
Also known asEUVD-2026-17847 (ENISA EUVD) · GHSA-gvrj-cjch-728p (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (Canonical Ltd.) lists Canonical Juju versions 3.2.0 up to but not including 3.6.20 and 4.0 up to but not including 4.0.4 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALmedium confidence
- EG Risk
- 76EG Risk 76/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)Severity100% × 45%Impact severity (EG Severity): CVSS 10.0 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.Automatability100% × 15%CISA's SSVC Automatable value: yes (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 yes (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 or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- 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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: 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.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (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
April 1, 2026
Last Modified
October 26, 2026
Advisory Details (1)
Auto-updated Oct 26, 2026Improper TLS Client/Server authentication and certificate verification on Database Cluster · Advisory · juju/juju · GitHub
https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728pPatch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/juju/juju | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/juju/juju | — |
| — |
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 71× 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 100 of 286 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. None are among the latest 100 rows. The 186 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-29 22:10 UTCEG score recompute
- 2026-10-29 22:10 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 21:56 UTCEG score recompute
- 2026-10-28 21:56 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 21:43 UTCEG score recompute
- 2026-10-27 21:43 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-26 21:26 UTCEG score recompute
- 2026-10-26 21:26 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-25 23:03 UTCEG score recompute
- 2026-10-25 23:03 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-25 14:28 UTCEG score recompute
- 2026-10-24 22:49 UTCEG score recompute
- 2026-10-24 22:49 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-23 22:36 UTCEG score recompute
- 2026-10-23 22:36 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-22 22:12 UTCEG score recompute
- 2026-10-22 22:12 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 moreShow fewer
- 2026-10-21 21:49 UTCEG score recompute
- 2026-10-21 21:49 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-20 21:12 UTCEG score recompute
- 2026-10-20 21:12 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-19 20:58 UTCEG score recompute
- 2026-10-19 20:58 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 19:14 UTCEG score recompute
- 2026-10-18 19:14 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 03:39 UTCEG score recompute
- 2026-10-17 19:00 UTCEG score recompute
- 2026-10-17 19:00 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 18:46 UTCEG score recompute
- 2026-10-16 18:45 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-15 15:48 UTCEG score recompute
- 2026-10-15 15:48 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-14 10:00 UTCEG score recompute
- 2026-10-14 10:00 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-13 08:08 UTCEG score recompute
- 2026-10-13 08:08 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 16:06 UTCEG score recompute
- 2026-10-12 07:53 UTCGHSA enrichmentGHSA-gvrj-cjch-728p · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 19:48 UTCEG score recompute
- 2026-10-11 17:02 UTCEG score recompute
- 2026-10-11 14:28 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-11 03:01 UTCOSV refresh
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-21 14:19 UTCOSV refresh
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-02 11:44 UTCOSV refresh
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/juju/juju
Same CWE
10 shownCWE-306 · CWE-287 · CWE-295
Frequently asked(5)
What is CVE-2026-4370?
When was the CVE record for CVE-2026-4370 published?
Is CVE-2026-4370 actively exploited?
What is the CVSS score of CVE-2026-4370?
How do I remediate CVE-2026-4370?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4370
Is Your Infrastructure Affected by CVE-2026-4370?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.