CVE-2026-4370

Improper TLS Client/Server authentication and certificate verification on Database Cluster

Published Apr 1, 2026 CVSS 3.1 · 10 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An attacker can join a Juju database cluster because the controller does not verify client certificates when a new node attempts to join. Once a node is accepted, the attacker has full read and write access to the database, allowing them to read confidential data, modify records, and potentially disrupt services. The weakness is an example of improper TLS authentication (CWE‑295) and failure to enforce authentication (CWE‑306).

Affected Systems

Canonical Juju versions from 3.2.0 through 3.6.19 and from 4.0 through 4.0.4 are affected. Versions prior to 3.2.0 and after 4.0.4 are not vulnerable according to the provided data.

Risk and Exploitability

With a CVSS score of 10, the vulnerability is rated as critical, but an EPSS score of less than 1% suggests a low current probability of exploitation. It is not listed in the CISA KEV catalog. The attack requires only network reachability to the controller’s Dqlite port, making it straightforward for an intruder on the same network or with access to an exposed port to exploit the flaw and gain complete control of the underlying database.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Juju to the latest released version that includes the TLS client authentication check (see the official advisory for the exact patch version).
  • Restrict network access to the Juju controller’s Dqlite port by configuring firewall rules or network segmentation to prevent exposure to untrusted networks.
  • Monitor cluster logs for unexpected peer join requests and remove any unauthorized nodes immediately.

Generated by OpenCVE AI on April 2, 2026 at 23:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gvrj-cjch-728p Juju has Improper TLS Client/Server authentication and certificate verification on Database Cluster
History
Type Values Removed Values Added
First Time appeared Canonical
Canonical juju
CPEs cpe:2.3:a:canonical:juju:*:*:*:*:*:*:*:*
Vendors & Products Canonical
Canonical juju
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values 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.
Title Improper TLS Client/Server authentication and certificate verification on Database Cluster
Weaknesses CWE-295
CWE-306
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-295

    Improper Certificate Validation

  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
canonical
Published
Updated
Apr 8, 2026, 7:27 AM
Reserved
Mar 18, 2026, 8:46 AM
Status
Analyzed
Published
Apr 1, 2026, 9:16 AM
Modified
Oct 26, 2026, 9:10 PM