CVE-2025-68152: Juju: Read All Controller Logs From Compromised Workload
Summary 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. There is a debug log endpoint in the API server that allows streaming of logs off of the controller. To access this endpoint you must be authentication and either be a machine agent, controller agent, controller admin or have model read permission.
Published Apr 3, 2026 · Updated Apr 27, 2026
Affected packages
github.com/juju/juju
- Ecosystem
- Go
- Affected
- < 0.0.0-20250623030540-c91a1f404695
- Fixed in
- 0.0.0-20250623030540-c91a1f404695
- Check
go list -m github.com/juju/juju
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
There is a debug log endpoint in the API server that allows streaming of logs off of the controller. To access this endpoint you must be authentication and either be a machine agent, controller agent, controller admin or have model read permission.
The problematic is the machine agent story. The rest of the other checks have a high enough degree of safety that an attacker can not move side ways in the controller when obtaining log files.
Details
A compromised workload machine is capable of obtaining logs for both the controller and any model under the controller at any log level they wish. A bad actor can use this information as signal for further attacks or possible gain secret information leaked out in debug and trace logs. On top of this they would also be able to receive the logs from the charm itself for which we have no control over.
- here is where the authorizer is defined for the endpoint.
- here is where the authorizer is checked.
- here and onwards is the amount of information the attacker can gain access to.
PoC
If an attacker compromises a workload machine, they will have access to the agent.conf file containing the credentials. This can then be used to obtain debug logs for any part of the controller.
Credited to tlm.
References
- https://github.com/juju/juju/security/advisories/GHSA-j6f6-jp3p-53mw
- https://github.com/juju/juju/commit/22cdcf6b54c2f371822e1c203d4f341be6c9589e
- https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3
- https://nvd.nist.gov/vuln/detail/CVE-2025-68152
- https://github.com/advisories/GHSA-j6f6-jp3p-53mw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-5412
Juju: CloudSpec method leaking cloud credentials
critical9.9Apr 10, 2026CVE-2026-5774
Juju: In-Memory Token Store for Discharge Tokens Lacks Concurrency Safety and Persistence
medium6.4Apr 10, 2026CVE-2025-68153
Juju has a resource poisoning vulnerability
high6.5Apr 3, 2026CVE-2026-4370
Juju has Improper TLS Client/Server authentication and certificate verification on Database Cluster
critical10.0No fixApr 2, 2026CVE-2026-32691
Juju affected by timing ownership claim attack on new external back-end secrets
medium5.3Mar 19, 2026CVE-2026-32692
Juju has unauthorized update of out-of-scope Vault secrets
high7.6Mar 19, 2026
