CVE-2025-53512 Sensitive log retrieval in Juju

Medium 6.5 Published Updated

Unauthorized users can access sensitive debug logs from the Juju controller due to missing authorization checks on the log endpoint.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-53512?

CVE-2025-53512 is a medium-severity missing authorization vulnerability in Canonical Juju, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The /log endpoint on a Juju controller lacked sufficient authorization checks, allowing unauthorized users to access debug messages that could contain sensitive information.

Weakness: CWE-285, CWE-200

Which versions are affected by CVE-2025-53512?

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

PackageAffectedFixed in
github.com/juju/juju GoAll versions0.0.0-20250619024904-402ff008dcc2
github.com/juju/juju GoAll versions0.0.0-20250619024904-402ff008dcc2
github.com/juju/juju GoAll versions0.0.0-20250619024904-402ff008dcc2

Products include Canonical Juju.

How do I fix CVE-2025-53512?

Upgrade github.com/juju/juju to 0.0.0-20250619024904-402ff008dcc2 or later.

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

Is CVE-2025-53512 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53512 exists.

Sources

Also known as GHSA-r64v-82fh-xc63, GO-2025-3806.

Is CVE-2025-53512 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free