https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T06:51:47.305204+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-281200 EUVD-2026-281200 2026-10-06T06:51:47.355077+00:00 EUVD-2026-281200 https://cve.radiocsirt.org/vuln/fkie_cve-2026-4370 fkie_cve-2026-4370 2026-10-06T06:51:47.355116+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-gvrj-cjch-728p GHSA-gvrj-cjch-728p — Juju has Improper TLS Client/Server authentication and certificate verification on Database Cluster 2026-10-06T06:51:47.355154+00:00

Affected: Go: github.com/juju/juju

### Impact Any Juju controller since 3.2.0.

An attacker with only route-ability to the target juju controller Dqlite cluster endpoint may join the Dqlite cluster, read and modify all information, including escalating privileges, open firewall ports etc.

This is due to not checking the client certificate, additionally, the client does not check the server's certificate (MITM attack possible), so anything goes.

https://github.com/juju/juju/blob/001318f51ac456602aef20b123684f1eeeae9a77/internal/database/node.go#L312-L324

#### PoC Using the tool referenced below.

Bootstrap a controller and show the users: ``` $ juju bootstrap lxd a Creating Juju controller "a" on lxd/localhost Looking for packaged Juju agent version 4.0.4 for amd64 <...> Launching controller instance(s) on localhost/localhost... - juju-fefd2b-0 (arch=amd64) Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 10.151.236.15:22 <...> Contacting Juju controller at 10.151.236.15 to verify accessibility...

Bootstrap complete, controller "a" is now available Controller machines are in the "controller" model

Now you can run juju add-model <model-name> to create a new model to deploy workloads. $ juju users Controller: a

Name Display name Access Date created Last connection admin* admin superuser 1 minute ago just now juju-metrics Juju Metrics login 1 minute ago never connected everyone@external ```

Join the cluster wit…