CVE-2026-66375

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
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

JFrog Security Advisories

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

Artifactory Self-Managed Releases

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

Vendor Advisories for CVE-2026-66375(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 26× in last 7d / 35× 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 12:47 UTCGHSA enrichment
  2. 2026-08-20 00:22 UTCEG score recompute
  3. 2026-08-20 00:22 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 12:00 UTCGHSA enrichment
  6. 2026-08-18 23:37 UTCEG score recompute
  7. 2026-08-18 23:37 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 11:15 UTCGHSA enrichment
  10. 2026-08-17 22:53 UTCEG score recompute
  11. 2026-08-17 22:53 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 10:31 UTCGHSA enrichment
  14. 2026-08-16 22:10 UTCEG score recompute
  15. 2026-08-16 22:10 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 09:49 UTCEG score recompute
  18. 2026-08-16 09:49 UTCGHSA enrichment
  19. 2026-08-15 21:28 UTCGHSA enrichment
  20. 2026-08-15 09:07 UTCEG score recompute
  21. 2026-08-15 09:07 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 20:45 UTCGHSA enrichment
  24. 2026-08-14 08:24 UTCEG score recompute
  25. 2026-08-14 08:24 UTCGHSA enrichment
Show 10 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 20:02 UTCGHSA enrichment
  3. 2026-08-13 07:41 UTCGHSA enrichment
  4. 2026-08-12 19:19 UTCEG score recompute
  5. 2026-08-12 19:19 UTCGHSA enrichment
  6. 2026-08-12 18:56 UTCEG score recompute
  7. 2026-08-12 18:56 UTCGHSA enrichment
  8. 2026-08-12 15:25 UTCEG score recompute
  9. 2026-08-12 15:13 UTCEG score recompute
  10. 2026-08-12 15:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-66375?
CVE-2026-66375 is a high vulnerability published on August 12, 2026. A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.
When was CVE-2026-66375 disclosed?
CVE-2026-66375 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-66375 actively exploited?
CVE-2026-66375 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 80.1% of all scored CVEs.
What is the CVSS score of CVE-2026-66375?
CVE-2026-66375 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-66375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66375, 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-66375

Explore →

Is Your Infrastructure Affected by CVE-2026-66375?

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

Start Free Scan →Browse All CVEs