CVE-2026-4370

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-02. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: Elevated riskExposed: 0

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

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.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
76(Attend)
EG Risk 76/100SSVC: Attend

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
Severity100% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

April 1, 2026

Last Modified

April 2, 2026

Advisory Details (1)

Auto-updated Sep 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Improper TLS Client/Server authentication and certificate verification on Database Cluster · Advisory · juju/juju · GitHub

https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
gogithub.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)
PackageVulnerable rangeFixed inDependents
github.com/juju/juju———

Weakness Classification(4)

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

Data Freshness Timeline

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

Showing the most recent 100 of 205 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Same product

1 shown

go:github.com/juju/juju

Frequently asked(5)

What is CVE-2026-4370?
CVE-2026-4370 is a critical vulnerability published on April 1, 2026. 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…
When was CVE-2026-4370 disclosed?
CVE-2026-4370 was first published in the National Vulnerability Database on April 1, 2026, with the most recent update on April 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4370 actively exploited?
CVE-2026-4370 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 68.4% of all scored CVEs.
What is the CVSS score of CVE-2026-4370?
CVE-2026-4370 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-4370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4370, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-4370

Explore →

Is Your Infrastructure Affected by CVE-2026-4370?

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

Start Free Scan →Browse All CVEs