CVE-2025-53513 Zip slip vulnerability in Juju

High 8.8 Published Updated

An attacker with a controller account can upload a malicious charm exploiting Zip Slip to execute code on target machines.

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-53513?

CVE-2025-53513 is a high-severity path traversal 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 /charms endpoint on a Juju controller lacked sufficient authorization checks, allowing any user with an account on the controller to upload a charm. Uploading a malicious charm that exploits a Zip Slip vulnerability could allow an attacker to gain access to a machine running a unit through the affected charm.

Weakness: CWE-22, CWE-24

Which versions are affected by CVE-2025-53513?

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-20250619215741-6356e984b82a
github.com/juju/juju GoAll versions0.0.0-20250619215741-6356e984b82a
github.com/juju/juju GoAll versions0.0.0-20250619215741-6356e984b82a

Products include Canonical Juju.

How do I fix CVE-2025-53513?

Upgrade github.com/juju/juju to 0.0.0-20250619215741-6356e984b82a or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2025-53513 being exploited?

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

Sources

Also known as GHSA-24ch-w38v-xmh8, GO-2025-3804.

Is CVE-2025-53513 in your software?

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

Check your SBOMs for free