Skip to main content
VulnerabilityPublished

CVE-2025-53513: Canonical Juju · Path Traversal: '../filedir

Affects Canonical JujuSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubjuju/jujupkg:github/juju/jujuOther threatsAffected
  • =2.0.0
  • =3.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate Restriction of Access: Limit Juju controller account creation and access strictly to trusted administrators and users with a clear operational need.
  2. Implement Strong Authentication and Monitoring: Enforce multi-factor authentication (MFA) for all Juju accounts and monitor charm upload activities for anomalies or unauthorized attempts.
  3. Apply Principle of Least Privilege: Review and reduce user privileges on the Juju controller to minimize the number of accounts capable of uploading charms.
  4. Validate and Sanitize Uploaded Charms: Until an official patch is available, implement manual or automated scanning of uploaded charms to detect path traversal patterns or suspicious archive contents.
  5. Network Segmentation: Isolate Juju controllers and units in secure network zones to limit potential lateral movement in case of compromise.
  6. Patch Management: Monitor Canonical’s advisories closely and apply official patches or updates as soon as they are released.
  7. Incident Response Preparedness: Prepare to respond to potential exploitation by having backups, forensic capabilities, and remediation plans ready.
  8. Engage with Canonical Support: Seek guidance and potential workarounds from Canonical to mitigate risk in the interim. These steps go beyond generic advice by focusing on access control tightening, proactive detection, and environment hardening tailored to Juju’s operational context.

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.

References

Community reviews

Loading reviews…