Juju zip slip vulnerability via authenticated endpoint

Exploitation

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

CVSS

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

EPSS

• CVE-2025-53513: 0.78% estimated exploitation activity in the next 30 days; percentile 55.86 (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 upload a charm to the /charms endpoint. No specific permissions are required - it's just sufficient for the user to exist in the controller user database. A charm which exploits the zip slip vulnerability may be used to allow such a user to get access to a machine running a unit using the affected charm. Details A controller exposes three charm-related HTTP API endpoints, as follows: - PUT/GET https://<controller-ip:17070/model-<model-uuid/charms/<nameofcharm-<hashofcharm - POST/GET https://<controller-ip:17070/model-<model-uuid/charms - GET https://<controller-ip:17070/charms These endpoints require Basic HTTP authentication credentials and will accept any valid user within the context of the controller. A user that has no specific permission or access granted can call all of these APIs. To reproduce: Download the ZIP file of an arbitrary charm eg https://github.com/juju/hello-juju-charm Download and install the following tool:…

Published by the source

9 Jul 2025, 15:29 UTC

Last modified by the source

26 Aug 2025, 20:20 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-24ch-w38v-xmh8

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

# Patch Next advisory brief: CVE-2025-53513

Advisory: Juju zip slip vulnerability via authenticated endpoint
IDs: CVE-2025-53513, GHSA-24ch-w38v-xmh8
Record: https://patchnext.com/advisories/cve-2025-53513 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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-20250619215741-6356e984b82a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juju/juju: affected < 0.0.0-20250619215741-6356e984b82a; fixed in 0.0.0-20250619215741-6356e984b82a

## 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-24ch-w38v-xmh8 (GitHub-reviewed advisory GHSA-24ch-w38v-xmh8 lists affected ranges: Go github.com/juju/juju >=0 <0.0.0-20250619215741-6356e984b82a)

Commands are suggestions: review each one before running it.