CVE-2025-53512: Juju vulnerable to sensitive log retrieval via authenticated endpoint without authorization
Impact Any user with a Juju account on a controller can read debug log messages from the /log endpoint. No specific permissions are required - it's just sufficient for the user to exist in the controller user database. The log messages may contain sensitive information.
Published Jul 9, 2025
Affected packages
github.com/juju/juju
- Ecosystem
- Go
- Affected
- < 0.0.0-20250619024904-402ff008dcc2
- Fixed in
- 0.0.0-20250619024904-402ff008dcc2
- Check
go list -m github.com/juju/juju
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Any user with a Juju account on a controller can read debug log messages from the /log endpoint. No specific permissions are required - it's just sufficient for the user to exist in the controller user database. The log messages may contain sensitive information.
Details
The /log endpoint is accessible at the following endpoints:
wss://<controller-ip>/logwss://<controller-ip>/model/<model-uuid>/log
In order to connect to these endpoints, the client must pass an X-Juju-Client-Version header that matches the current version and pass credentials in a Basic Authorization header. Once connected, the service will stream log events even though the user is not authorised to view them.
To reproduce:
juju bootstrap
juju add-user testuser
juju change-user-password testuserRun the wscat command below to connect to wss://<controller-ip>:17070/api. Update the JSON payload to include the username and password that were created above.
wscat --no-check -c wss://contorller-ip:17070/model/modelUUID/api
{ "type": "Admin", "request": "Login", "version": 3, "params": { "client-
version": "3.6.1.0", "auth-tag": "user-testuser", "credentials": "
password" } }Observe that the connection fails due to a lack of permissions.
Run the command below to connect to the log endpoint. Note that the credentials are passed in the --auth flag.
wscat --auth user-testuser:password -H "X-Juju-ClientVersion: 3.6.4" --no-check -c wss://<controller-ip>:17070/logObserve that the logs are returned in the server’s response.
Code
The /log handlers are registered here https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L867 https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L980
And the only auth required is that the incoming request be for an authenticated user
https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L713
but no specific permission checks are done.
Workarounds
There are no workarounds.
References
Credited to wallyworld, hpidcock.
References
- https://github.com/juju/juju/security/advisories/GHSA-r64v-82fh-xc63
- https://nvd.nist.gov/vuln/detail/CVE-2025-53512
- https://github.com/juju/juju/commit/402ff008dcc2cb57f4441968628637efb5c2a662
- https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3
- https://github.com/advisories/GHSA-r64v-82fh-xc63
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-68152
Juju: Read All Controller Logs From Compromised Workload
medium4.9Apr 3, 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, 2026
