10.0
CRITICAL CVSS 3.1
CVE-2026-4370
Improper TLS Client/Server authentication and certificate verification on Database Cluster
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.

INFO

Published Date :

April 1, 2026, 9:16 a.m.

Last Modified :

April 1, 2026, 9:16 a.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-4370 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 CRITICAL cc1ad9ee-3454-478d-9317-d3e869d708bc
CVSS 3.1 CRITICAL [email protected]
Solution
Update Juju to a patched version to enforce proper TLS client and server authentication.
  • Update Juju to a version after 3.6.19 or 4.0.4.
  • Ensure TLS is correctly configured for the Dqlite database cluster.
  • Validate client certificate authentication for new cluster nodes.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-4370.

URL Resource
https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-4370 is associated with the following CWEs:

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-4370 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-4370 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Apr. 01, 2026

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    Added CWE CWE-295
    Added CWE CWE-306
    Added Reference https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.