CVE-2026-66016: Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifes

Routine

MEDIUM 6.7UPGRADE

CVE-2026-66016 is a medium-severity flaw (CVSS 6.7) affecting artifactory. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.7 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.1% (top 98%)
CISA exploited list	No
Weakness	CWE-312
Published	2026-08-12
Last modified	2026-10-23

Publisher (CNA): JFrog · Vendor: jfrog

Am I affected?

Timeline

2026-08-12 16:17 UTCPublished CVE record published
2026-10-23 20:10 UTCUpdated Record last modified

jfrog artifactory UPGRADE

Affected: < 7.146.35 · >= 7.161.0 and < 7.161.16

Fixed in: 7.146.35, 7.161.16

Safe to downgrade to: a release before 7.161.0

1. Check installed version

apt-cache policy artifactory || rpm -q artifactory || artifactory --version

2. UPGRADE to 7.146.35 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade artifactory

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade artifactory

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 7.161.0 (Debian / Ubuntu)

apt-cache madison artifactory sudo apt install artifactory=<VERSION_BEFORE_7.161.0> sudo apt-mark hold artifactory

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list artifactory sudo dnf downgrade artifactory-<VERSION_BEFORE_7.161.0> sudo dnf versionlock add artifactory

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-66016?

artifactory: upgrade to 7.146.35, 7.161.16. Exact commands for each OS are on this page.

Is CVE-2026-66016 being exploited?

CVE-2026-66016 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-66016 affect?

CVE-2026-66016 affects artifactory. Severity is medium (CVSS 6.7). Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.

How urgent is CVE-2026-66016?

Priority 24/100. No elevated risk signals yet.

Related CVEs

CVE-2026-42016 HIGH 8.1 EXPLOITED UPGRADE JFrog Artifactory Incorrect Authorization Vulnerability
CVE-2026-65617 HIGH 8.8 UPGRADE A deserialization weakness in JFrog Artifactory package handling could allow a low-privileged user to impact c
CVE-2026-65921 HIGH 8.8 UPGRADE A path validation weakness in archive extraction/write handling allows entries with traversal sequences to be
CVE-2026-66014 HIGH 8.8 UPGRADE JFrog Artifactory contains an authentication handling weakness in internal request processing that, under spec
CVE-2026-42017 HIGH 8.8 UPGRADE An event-handling weakness in JFrog Artifactory could expose privileged authorization material to a lower-priv

References

← Back to latest CVEs