CVE-2025-0928: Canonical Juju · Improper Authorization
Affects Canonical JujuSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 3.6.8 or 2.9.52 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.6.8, 2.9.52
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade juju/juju to 3.6.8 or 2.9.52.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjuju/jujupkg:github/juju/jujuOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade Juju installations to versions 3.6.8 or 2.9.52 or later, where the authorization flaw is fixed. Until upgrades are applied, organizations should restrict controller user access strictly to trusted personnel and enforce the principle of least privilege, ensuring only necessary users have authenticated controller access. Implement strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. Monitor Juju controller logs for unusual agent binary uploads or model modifications that could indicate exploitation attempts. Network segmentation should be applied to isolate Juju controllers and managed models from general user networks. Additionally, organizations should conduct audits of user permissions within Juju to confirm no excessive privileges are granted. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect anomalous behaviors indicative of remote code execution. Finally, maintain an incident response plan tailored to cloud orchestration compromises to rapidly contain and remediate any exploitation.
Description
In Juju versions prior to 3.6.8 and 2.9.52, any authenticated controller user was allowed to upload arbitrary agent binaries to any model or to the controller itself, without verifying model membership or requiring explicit permissions. This enabled the distribution of poisoned binaries to new or upgraded machines, potentially resulting in remote code execution.