Canonical Juju up to 2.9.56/3.6.20 CloudSpec API improper authorization

Summaryinfo

A vulnerability identified as critical has been detected in Canonical Juju up to 2.9.56/3.6.20. The affected element is an unknown function of the component CloudSpec API. The manipulation leads to improper authorization. This vulnerability is listed as CVE-2026-5412. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Canonical Juju up to 2.9.56/3.6.20. It has been rated as critical. This issue affects some unknown functionality of the component CloudSpec API. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade. An authenticated user can call the CloudSpec API method to extract the cloud credentials used to bootstrap the controller. This allows a low-privileged user to access sensitive credentials. This issue is resolved in Juju versions 2.9.57 and 3.6.21.

The weakness was presented by Ales Stimec as GHSA-w5fq-8965-c969. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-5412 since 04/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

Upgrading to version 2.9.57 or 3.6.21 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Canonical

Name

• Juju

Version

• 2.9.0
• 2.9.1
• 2.9.2
• 2.9.3
• 2.9.4
• 2.9.5
• 2.9.6
• 2.9.7
• 2.9.8
• 2.9.9
• 2.9.10
• 2.9.11
• 2.9.12
• 2.9.13
• 2.9.14
• 2.9.15
• 2.9.16
• 2.9.17
• 2.9.18
• 2.9.19
• 2.9.20
• 2.9.21
• 2.9.22
• 2.9.23
• 2.9.24
• 2.9.25
• 2.9.26
• 2.9.27
• 2.9.28
• 2.9.29
• 2.9.30
• 2.9.31
• 2.9.32
• 2.9.33
• 2.9.34
• 2.9.35
• 2.9.36
• 2.9.37
• 2.9.38
• 2.9.39
• 2.9.40
• 2.9.41
• 2.9.42
• 2.9.43
• 2.9.44
• 2.9.45
• 2.9.46
• 2.9.47
• 2.9.48
• 2.9.49
• 2.9.50
• 2.9.51
• 2.9.52
• 2.9.53
• 2.9.54
• 2.9.55
• 2.9.56
• 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
• 3.6.20

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion