An authenticated user may initiate repository migration operations without required repository permissions, potentially causing information disclosure, unauthorized state changes, and service disruption. Fixed versions address the issue.
CVE-2026-69104
Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(high)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity76% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026Artifactory Self-Managed Releases
https://docs.jfrog.com/releases/docs/artifactory-self-managed-releasesVendor Advisories for CVE-2026-69104(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 21× in last 7d / 21× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:33 UTCGHSA enrichment
- 2026-08-29 10:38 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEG score recompute
- 2026-08-28 21:42 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 11:06 UTCGHSA enrichment
- 2026-08-27 22:10 UTCEG score recompute
- 2026-08-27 22:10 UTCGHSA enrichment
- 2026-08-27 09:15 UTCGHSA enrichment
- 2026-08-26 20:19 UTCEG score recompute
- 2026-08-26 20:19 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 07:24 UTCGHSA enrichment
- 2026-08-25 18:28 UTCEG score recompute
- 2026-08-25 18:28 UTCGHSA enrichment
- 2026-08-25 17:55 UTCEG score recompute
- 2026-08-25 17:55 UTCGHSA enrichment
- 2026-08-25 15:21 UTCEG score recompute
- 2026-08-25 15:15 UTCEG score recompute
- 2026-08-25 15:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-69104?
When was CVE-2026-69104 disclosed?
Is CVE-2026-69104 actively exploited?
What is the CVSS score of CVE-2026-69104?
How do I remediate CVE-2026-69104?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-69104
Is Your Infrastructure Affected by CVE-2026-69104?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.