juju vulnerabilities and fixes
Recent CVEs affecting juju, with upgrade or downgrade steps. 3 tracked.
juju has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-04-10. Highest priority: CVE-2026-4370 (score 53/100).
- CVE-2026-4370 CRITICAL 10.0 UPGRADE A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where
- CVE-2026-5412 CRITICAL 9.9 UPGRADE In Juju versions prior to 2.9.57 and 3.6.21, an authorization issue exists in the Controller facade
- CVE-2026-5774 MEDIUM 6.4 UPGRADE Improper synchronization of the userTokens map in the API server in Canonical Juju 4.0.5, 3.6.20, and 2.9.56 m
FAQ
How do I fix juju vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is juju being exploited right now?
None of the tracked juju CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which juju CVE should I patch first?
CVE-2026-4370 currently ranks highest (53/100): A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where.