CVE-2026-5774GHSA-7M55-2HR4-PW78GO-2026-5228
Juju API Server Denial of Service and Authentication Replay via Unsynchronized Token Map
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.9.57, 3.6.21, 4.0.6, 0.0.0-20260408003526-d395054dc2c3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- juju
From 2.0.0 · fixed in 2.9.57; From 3.0.0 · fixed in 3.6.21; From 4.0.0 · fixed in 4.0.6
- github.com/juju/jujuGo
fixed in 0.0.0-20260408003526-d395054dc2c3