Canonical Juju up to 2.9.56/3.6.20/4.0.5 API Server race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Canonical Juju up to 2.9.56/3.6.20/4.0.5. It has been rated as problematic. This issue affects some unknown processing of the component API Server. Performing a manipulation results in race condition. This vulnerability is identified as CVE-2026-5774. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Canonical Juju up to 2.9.56/3.6.20/4.0.5. It has been classified as problematic. This affects an unknown function of the component API Server. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on availability. The summary by CVE is:
Improper synchronization of the userTokens map in the API server in Canonical Juju 4.0.5, 3.6.20, and 2.9.56 may allow an authenticated user to possibly cause a denial of service on the server or possibly reuse a single-use discharge token.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-5774 since 04/08/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2.9.57, 3.6.21 or 4.0.6 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
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
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.0.5
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Juju 2.9.57/3.6.21/4.0.6
Patch: github.com
Timeline
04/08/2026 CVE reserved04/10/2026 Advisory disclosed
04/10/2026 VulDB entry created
04/10/2026 VulDB entry last update
Sources
Advisory: GHSA-7m55-2hr4-pw78Status: Confirmed
CVE: CVE-2026-5774 (🔒)
GCVE (CVE): GCVE-0-2026-5774
GCVE (VulDB): GCVE-100-356811
Entry
Created: 04/10/2026 15:49Changes: 04/10/2026 15:49 (68)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.