CVE-2026-4370 | Canonical Juju up to 3.6.19/4.0.3 certificate validation

VDB-354615 · CVE-2026-4370 · GCVE-0-2026-4370 CANONICAL JUJU UP TO 3.6.19/4.0.3 CERTIFICATE VALIDATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 8.5 $0-$5k 2.42+ Summaryinfo A vulnerability identified as critical has been detected in Canonical Juju up to 3.6.19/4.0.3. This affects an unknown function. Performing a manipulation results in certificate validation. This vulnerability is known as CVE-2026-4370. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component. Detailsinfo A vulnerability was found in Canonical Juju up to 3.6.19/4.0.3. It has been classified as critical. This affects some unknown functionality. The manipulation with an unknown input leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: 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. The weakness was published by Harry Pidcock. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-4370 since 03/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1587.003 according to MITRE ATT&CK. Upgrading to version 3.6.20 or 4.0.4 eliminates this vulnerability. Productinfo Vendor Canonical Name Juju Version 3.6.0 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.6.10 3.6.11 3.6.12 3.6.13 3.6.14 3.6.15 3.6.16 3.6.17 3.6.18 3.6.19 4.0.0 4.0.1 4.0.2 4.0.3 License open-source CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 8.6 VulDB Meta Temp Score: 8.5 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 10.0 CNA Vector (canonical): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Certificate validation CWE: CWE-295 / CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Juju 3.6.20/4.0.4 Timelineinfo 03/18/2026 CVE reserved 04/01/2026 +13 days Advisory disclosed 04/01/2026 +0 days VulDB entry created 04/01/2026 +0 days VulDB entry last update Sourcesinfo Advisory: github.com Researcher: Harry Pidcock Status: Confirmed CVE: CVE-2026-4370 (🔒) GCVE (CVE): GCVE-0-2026-4370 GCVE (VulDB): GCVE-100-354615 Entryinfo Created: 04/01/2026 10:48 Changes: 04/01/2026 10:48 (64) Complete: 🔍 Cache ID: 99:F07:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸