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.
References
| Link | Resource |
|---|---|
| https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p | Exploit Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
02 Apr 2026, 20:24
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Canonical
Canonical juju |
|
| CPE | cpe:2.3:a:canonical:juju:*:*:*:*:*:*:*:* | |
| References | () https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p - Exploit, Vendor Advisory |
01 Apr 2026, 09:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-01 09:16
Updated : 2026-04-02 20:24
NVD link : CVE-2026-4370
Mitre link : CVE-2026-4370
CVE.ORG link : CVE-2026-4370
JSON object : View
Products Affected
canonical
- juju