Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Canonical | Juju | 2.0.0 – < 2.9.57, 3.0.0 – < 3.6.21, 4.0.0 – < 4.0.6 | 2.9.57 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | github.com/juju/juju | < 0.0.0-20260408003526-d395054dc2c3 | 0.0.0-20260408003526-d395054dc2c3 | GHSA-7m55-2hr4-pw78 |
Advisories 1
- openSUSE-SU-2026:21483-1 Security update for govulncheck-vulndb SUSE / openSUSE Security Updates · Jul 31, 2026
References
- In-Memory Token Store for Discharge Tokens Lacks Concurrency Safety and Persistence vdb-entry vendor-advisory
- https://github.com/juju/juju/pull/22206 patch issue-tracking
- https://github.com/juju/juju/pull/22205 patch issue-tracking