CVE-2026-66016 json
Rendered Artifactory Helm manifests may contain generated TLS private keys
published 2mo ago modified 18d ago also EUVD-2026-57259
- cvss
- 6.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.
Patch / fix
- jfrog artifactory 7.146.35, 7.161.16
Is CVE-2026-66016 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- jfrog artifactory
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
docs.jfrog.com
/releases/docs/jfrog-security-advisories
vendor-advisory
-
docs.jfrog.com
/releases/docs/artifactory-self-managed-releases
vendor-advisory, release-notes
Sources
- CVE List CVE-2026-66016
- NVD CVE-2026-66016
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.