CVE-2025-68152 Juju: Read All Controller Logs From Compromised Workload

What is CVE-2025-68152?

CVE-2025-68152 is a medium-severity missing authorization vulnerability in juju, published on 3 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, it is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19.

Weakness: CWE-863

Which versions are affected by CVE-2025-68152?

3 open source packages ship an affected version, including github.com/juju/juju. It affects 1 product.

Products include Canonical Juju.

How do I fix CVE-2025-68152?

Upgrade github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2025-68152 being exploited?

There is no known exploitation of CVE-2025-68152 in the wild and no public exploit code.

Other vulnerabilities in juju

• CVE-2026-4370 Improper TLS Client/Server authentication and certificate verification on Database Cluster Critical 10.0
• CVE-2026-5412 Juju CloudSpec API could leak senstive information Critical 9.9
• CVE-2017-9232 Juju uses a UNIX domain socket without setting appropriate permissions Critical 9.8
• CVE-2026-32693 Unauthorized access to Kubernetes secrets in Juju High 8.8
• CVE-2025-0928 Arbitrary executable upload via authenticated endpoint High 8.8

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-j6f6-jp3p-53mw, GO-2026-5451.