Skip to main content
CVE-2025-6224VulnerabilityPublished

CVE-2025-6224: Canonical Juju utils · Cleartext Storage of Sensitive Information

Affects Canonical Juju utilsSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubjuju/utilspkg:github/juju/utilsOther threatsAffected
  • =4.0.1
Fixed in–

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

AI-suggested

To mitigate this vulnerability, European organizations should immediately audit their use of Juju utils version 4.0.1 and identify any deployments where certificate generation and transmission occur. Until an official patch is released, organizations should enforce the use of encrypted communication channels such as TLS for all Juju-related network traffic to prevent interception of sensitive data. Network segmentation and the use of VPNs or secure tunnels can reduce exposure to network sniffing attacks. Additionally, organizations should implement strict monitoring and logging of certificate generation and usage to detect anomalies. Rotating and revoking any certificates or private keys potentially exposed is critical to limit the window of exploitation. User training to minimize risky interactions that could trigger the vulnerability is also recommended. Finally, organizations should track Canonical's advisories closely for patches or updates addressing this vulnerability and apply them promptly once available.

Description

Certificate generation in juju/utils using the cert.NewLeaf function could include private information. If this certificate were then transferred over the network in plaintext, an attacker listening on that network could sniff the certificate and trivially extract the private key from it.

References

Community reviews

Loading reviews…