API server crash and token replay via race
Published Apr 10, 2026 · Updated Apr 10, 2026
Race condition in Canonical Juju 2.9.56, 3.6.20, and 4.0.5 allows remote authenticated users to crash the API server. The localLoginHandlers userTokens map is read, written, and deleted by concurrent HTTP handler goroutines without a lock, and its read-then-delete sequence is not atomic. A valid discharge token and concurrent requests are required; exploitation terminates the API server or accepts the single-use token more than once.
Summary
What happened
Race condition in Canonical Juju 2.9.56, 3.6.20, and 4.0.5 allows remote authenticated users to crash the API server. The localLoginHandlers userTokens map is read, written, and deleted by concurrent HTTP handler goroutines without a lock, and its read-then-delete sequence is not atomic. A valid discharge token and concurrent requests are required; exploitation terminates the API server or accepts the single-use token more than once.
The record
- CVE
- CVE-2026-5774
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- Canonical
- Product
- Juju
- Classifications
- CWE-362, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.9.57
- Affected versionversion=3.0.0 <3.6.21
- Affected versionversion=4.0.0 <4.0.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Concurrent discharge-request proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo