Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS vector (AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H) indicates this is a network-accessible vulnerability requiring low privilege authentication and high attack complexity with partial attacker timing control, resulting in complete availability impact but no confidentiality or integrity loss. The EPSS score of 6.1 suggests moderate exploitation likelihood in the wild. Critically, this vulnerability requires authenticated access (PR:L), which narrows the threat actor pool to users with valid credentials, reducing real-world risk compared to unauthenticated vulnerabilities. The partial timing requirement (AT:P) makes reliable exploitation difficult in practice. However, the availability impact is severe-a successful attack disables the API server for all users. The race condition nature means automated scanning cannot detect vulnerability presence, only version inventory. For environments where Juju API server stability is critical and where authentication credentials are loosely controlled, this poses moderate-to-high priority. For restricted environments with strong authentication, priority is lower. |
| Exploit ScenarioDerived | An authenticated user with low-privilege access to a Juju environment crafts multiple concurrent requests to the API server targeting token validation endpoints. By timing the requests to hit a narrow race condition window in the userTokens map synchronization, the attacker either causes the API server to crash or become unresponsive (DoS), or successfully reuses a discharge token that should have been single-use, bypassing authentication controls for subsequent operations. No public proof-of-concept code has been identified, but the race condition is reliable enough that exploitation is feasible for attackers with knowledge of Juju's internals. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 10, 2026
Improper synchronization of the userTokens map in Canonical Juju API server (versions 4.0.5, 3.6.20, and 2.9.56) enables authenticated users to trigger denial of service or reuse single-use discharge tokens due to a race condition. The vulnerability requires low privilege authentication and partial attacker timing control but allows complete availability impact to the server. EPSS score of 6.1 reflects moderate real-world exploitation risk, though no public exploit code or active exploitation has been confirmed.
RemediationAI
Upgrade to patched versions immediately: Juju 4.0.6 or later for 4.0.x deployments, Juju 3.6.21 or later for 3.6.x deployments, and Juju 2.9.57 or later for 2.9.x deployments. Fixes are available in upstream pull requests #22206 and #22205 at https://github.com/juju/juju. Consult the official security advisory at https://github.com/juju/juju/security/advisories/GHSA-7m55-2hr4-pw78 for detailed upgrade instructions and verification steps. As a temporary mitigation (not a substitute for patching), restrict network access to the Juju API server to trusted administrative networks only, limiting exposure to authenticated attackers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability stems from CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), affecting the authentication token management subsystem in Juju's API server. The userTokens map lacks proper synchronization mechanisms, creating a time-of-check-time-of-use (TOCTOU) race condition window. When multiple concurrent requests access the map during token validation or discharge token processing, an authenticated attacker can exploit the race to either cause the server to become unavailable or replay a single-use discharge token that should have been invalidated after first use. This is a classic synchronization flaw in concurrent systems where shared mutable state is accessed without adequate locking or atomic operations.
Know when Juju gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Primary rating from Vendor (canonical).
CVSS VectorVendor: canonical
Lifecycle Timeline
2DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Juju before 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3 uses a UNIX domain socket without setting appropriate pe
In Juju versions prior to 3.6.8 and 2.9.52, any authenticated controller user was allowed to upload arbitrary agent bina
The /charms endpoint on a Juju controller lacked sufficient authorization checks, allowing any user with an account on t
JUJU_CONTEXT_ID is a predictable authentication secret. Rated high severity (CVSS 8.0), this vulnerability is low attack
The /log endpoint on a Juju controller lacked sufficient authorization checks, allowing unauthorized users to access deb
Unauthenticated remote database cluster compromise in Canonical Juju (versions 3.2.0-3.6.19 and 4.0-4.0.4) allows comple
An authorization bypass vulnerability in Canonical's Juju versions 3.0.0 through 3.6.18 allows authenticated users with
An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged
An authorization bypass vulnerability exists in the Vault secrets back-end implementation of Canonical's Juju orchestrat
Canonical Juju 4.0 through 4.0.15 leaves the model unit-resources download route without an authorization check, so any
Unauthorized resource modification in Juju application orchestration engine allows any authenticated controller user to
Juju application orchestration engine versions 2.9 to 2.9.55 and 3.6 to 3.6.18 allow a compromised workload machine to r
Same weakness CWE-362 – Race Condition
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
EUVD-2026-21366
GHSA-7m55-2hr4-pw78
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB