CVE-2026-4370: critical vulnerability in Canonical Juju
Improper TLS Client/Server authentication and certificate verification on Database Cluster
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 10epss 0.4%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Affected products
Canonical · JujuRelated CVEs — Canonical Juju
In the same product, most dangerous first.
CVE-2025-53513HIGHZip slip vulnerability in JujuEPSS 0.8%CVE-2025-0928HIGHArbitrary executable upload via authenticated endpointEPSS 0.7%CVE-2026-5412CRITICALJuju CloudSpec API could leak senstive informationEPSS 0.5%CVE-2025-53512MEDIUMSensitive log retrieval in JujuEPSS 0.4%CVE-2026-32693HIGHUnauthorized access to Kubernetes secrets in JujuEPSS 0.4%CVE-2026-93336HIGHMissing authorization in the unit resources download route in Juju controllersEPSS 0.3%