CVE-2025-68153 Canonical CVE debrief

Who should care

Administrators and users of Juju 2.9 to 2.9.55 and 3.6 to 3.6.18 should apply patches to prevent authenticated users from modifying resources. Additionally, security teams and vulnerability management teams should review the vulnerability and apply necessary mitigations.

Technical summary

CVE-2025-68153 is a vulnerability in Juju, an open-source application orchestration engine. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, any authenticated user, machine, or controller under a Juju controller can modify the resources of an application within the entire controller. This issue has been patched in versions 2.9.56 and 3.6.19. The vulnerability allows for unauthorized resource modification, potentially leading to security breaches. Users should apply patches to prevent exploitation.

Defensive priority

High priority due to the potential for authenticated users to modify resources, with a CVSS score of 7.1.

Recommended defensive actions

• Apply patches to Juju versions 2.9.55 and 3.6.18 or earlier
• Restrict access to authenticated users and machines under the Juju controller
• Monitor for suspicious activity related to resource modifications
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail provide information on the vulnerability and its patches. The GitHub commit and advisory provide additional mitigation details. Evidence is limited, and defenders should verify affected Juju deployments, review official advisories, and monitor for suspicious activity related to resource modifications.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.