Skip to content
Fencer Intel
medium 6.5

CVE-2025-6224 json

Key leakage in juju/utils certificates

published last yr. modified 4mo ago also GHSA-h34r-jxqm-qgpr , GO-2025-3798 , EUVD-2025-19609

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/juju/utils/v4/cert 4.0.4
  • go github.com/juju/utils/v4 4.0.4
  • canonical juju/utils 4.0.4
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1

opensuse advisories openSUSE-SU-2025:15405-1

Is CVE-2025-6224 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/juju/utils/security/advisories/GHSA-h34r-jxqm-qgpr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/juju/utils/v4/cert
<4.0.4
4.0.4
go github.com/juju/utils
all versions
 no fix listed
go github.com/juju/utils/v2
all versions
 no fix listed
go github.com/juju/utils/v3
all versions
 no fix listed
go github.com/juju/utils/v4
<4.0.4
4.0.4

Affected products

  • Canonical Juju utils

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.