# CVE-2025-53513: Zip slip vulnerability in Juju

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

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-24ch-w38v-xmh8, GO-2025-3804

## 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 (Improper Limitation of a Pathname to a Restricted Directory), CWE-24 (Path Traversal: '../filedir')

## 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.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20250619215741-6356e984b82a |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20250619215741-6356e984b82a |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20250619215741-6356e984b82a |

Products: Canonical Juju.

## How do I fix CVE-2025-53513?

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

## Is CVE-2025-53513 being exploited?

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

## Other vulnerabilities in Canonical Juju

- [CVE-2026-4370](https://insights.sbomify.com/CVE-2026-4370/): Improper TLS Client/Server authentication and certificate verification on Database Cluster (critical 10.0)
- [CVE-2026-5412](https://insights.sbomify.com/CVE-2026-5412/): Juju CloudSpec API could leak senstive information (critical 9.9)
- [CVE-2017-9232](https://insights.sbomify.com/CVE-2017-9232/): Juju uses a UNIX domain socket without setting appropriate permissions (critical 9.8)
- [CVE-2026-32693](https://insights.sbomify.com/CVE-2026-32693/): Unauthorized access to Kubernetes secrets in Juju (high 8.8)
- [CVE-2025-0928](https://insights.sbomify.com/CVE-2025-0928/): Arbitrary executable upload via authenticated endpoint (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53513 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53513 exists.

Affected packages and fixed versions:
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20250619215741-6356e984b82a
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20250619215741-6356e984b82a
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20250619215741-6356e984b82a

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53513/ (Markdown: https://insights.sbomify.com/CVE-2025-53513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53513
- OSV: https://osv.dev/vulnerability/CVE-2025-53513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53513/
Summaries are generated and may contain mistakes; the official description above is the record.