Critical severity · published Apr 1, 2026
CVE-2026-4370
Improper TLS Client/Server authentication and certificate verification on Database Cluster
10.0
CVSS
0.4%
EPSS
No
On KEV
Description
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 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 32% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JU
Juju · Canonical
3.2.0 before 3.6.20; 4.0 before 4.0.4 · source: vendor, NVD
Affected product
JU
Juju
Canonical
More from Juju
9.8
CVE-2017-9232
Juju before 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3 uses a UNIX domain socket without setting appropriate permissions, allowing privilege escalation by users on the…
8.8
CVE-2026-32693
Unauthorized access to Kubernetes secrets in Juju
8.8
CVE-2025-0928
In Juju versions prior to 3.6.8 and 2.9.52, any authenticated controller user was allowed to upload arbitrary agent binaries to any model or to the controller itself, without…
8.0
CVE-2024-7558
JUJU_CONTEXT_ID is a predictable authentication secret
7.5
CVE-2015-1316
Juju Core's Joyent provider before version 1.25.5 uploads the user's private ssh key