Juju vulnerable to sensitive log retrieval via authenticated endpoint without authorization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2025-53512: 0.38% estimated exploitation activity in the next 30 days; percentile 31.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/log - wss://<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: Run 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. Observe that the connection fails due to a lack of permissions. Run the command below to connect to the log endpoint. Note that…

Published by the source

9 Jul 2025, 15:30 UTC

Last modified by the source

9 Jul 2025, 15:31 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r64v-82fh-xc63

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53512

Advisory: Juju vulnerable to sensitive log retrieval via authenticated endpoint without authorization
IDs: CVE-2025-53512, GHSA-r64v-82fh-xc63
Record: https://patchnext.com/advisories/cve-2025-53512 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juju/juju 0.0.0-20250619024904-402ff008dcc2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juju/juju: affected < 0.0.0-20250619024904-402ff008dcc2; fixed in 0.0.0-20250619024904-402ff008dcc2

## Suggested inspection (read-only)
- Go github.com/juju/juju: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juju/juju.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r64v-82fh-xc63 (GitHub-reviewed advisory GHSA-r64v-82fh-xc63 lists affected ranges: Go github.com/juju/juju >=0 <0.0.0-20250619024904-402ff008dcc2)

Commands are suggestions: review each one before running it.