CVE-2026-66016

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreHIGH confidence

Score 6.7 from GitHub Security Advisory published 2026-08-12. a secondary CVSS source baseline 6.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
6.7
EG Score
6.7(high)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

Artifactory Self-Managed Releases

https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases
generic

JFrog Security Advisories

https://docs.jfrog.com/releases/docs/jfrog-security-advisories

Vendor Advisories for CVE-2026-66016(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:21 UTCGHSA enrichment
  3. 2026-08-19 22:00 UTCGHSA enrichment
  4. 2026-08-18 21:39 UTCGHSA enrichment
  5. 2026-08-17 21:06 UTCEG score recompute
  6. 2026-08-17 21:05 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 20:44 UTCEG score recompute
  9. 2026-08-16 20:44 UTCGHSA enrichment
  10. 2026-08-15 20:23 UTCEG score recompute
  11. 2026-08-15 20:23 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 20:01 UTCEG score recompute
  14. 2026-08-14 20:01 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 19:40 UTCGHSA enrichment
  17. 2026-08-12 19:19 UTCEG score recompute
  18. 2026-08-12 19:19 UTCGHSA enrichment
  19. 2026-08-12 18:56 UTCEG score recompute
  20. 2026-08-12 18:56 UTCGHSA enrichment
  21. 2026-08-12 16:34 UTCEG score recompute
  22. 2026-08-12 15:36 UTCEG score recompute
  23. 2026-08-12 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66016?
CVE-2026-66016 is a medium vulnerability published on August 12, 2026. Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users.
When was CVE-2026-66016 disclosed?
CVE-2026-66016 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66016 actively exploited?
CVE-2026-66016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.8% of all scored CVEs.
What is the CVSS score of CVE-2026-66016?
CVE-2026-66016 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2026-66016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66016

Explore →

Is Your Infrastructure Affected by CVE-2026-66016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs