CVE-2026-92615

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreHIGH confidence

Score 6.6 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 6.6; sources differ by 0.0.

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

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

A flaw was found in flightctl. The configureRepoHTTPSClient() function in the device-render worker builds a per-repository tls.Config (which may include InsecureSkipVerify, a custom CA bundle, or tenant-supplied mTLS client certificates) and installs it into go-git's process-global client.Protocols map via gitclient.InstallProtocol("https", ...). Because the worker renders devices for multiple organizations concurrently from a shared goroutine pool, whichever tenant's repository configuration is written last wins for all in-flight git.Clone calls. This race condition can cause one tenant's TLS settings, including InsecureSkipVerify or mTLS client credentials, to leak into another tenant's git operations.

CVSS v3
6.6
EG Score
6.6(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
Severity66% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: redhat.
redhat

2518323 – (CVE-2026-92615) CVE-2026-92615 flightctl: flightctl: Package-global go-git HTTPS transport mutated per-repo -- cross-tenant TLS-config bleed

https://bugzilla.redhat.com/show_bug.cgi?id=2518323
redhat Patch Available

CVE-2026-92615 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-92615

Vendor Advisories for CVE-2026-92615(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 13× in last 7d / 13× 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-09-18 19:30 UTCEG score recompute
  2. 2026-09-18 19:30 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 18:00 UTCEG score recompute
  6. 2026-09-17 18:00 UTCGHSA enrichment
  7. 2026-09-17 15:54 UTCEG score recompute
  8. 2026-09-17 15:54 UTCGHSA enrichment
  9. 2026-09-16 19:45 UTCEG score recompute
  10. 2026-09-16 19:45 UTCGHSA enrichment
  11. 2026-09-16 16:31 UTCEG score recompute
  12. 2026-09-16 15:36 UTCEG score recompute
  13. 2026-09-16 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92615?
CVE-2026-92615 is a medium vulnerability published on September 16, 2026. A flaw was found in flightctl. The configureRepoHTTPSClient() function in the device-render worker builds a per-repository tls.Config (which may include InsecureSkipVerify, a custom CA bundle, or tenant-supplied mTLS client certificates) and installs it into go-git's process-global client.Protocols…
When was CVE-2026-92615 disclosed?
CVE-2026-92615 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92615 actively exploited?
CVE-2026-92615 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-92615?
CVE-2026-92615 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-92615?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92615, 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-92615

Explore →

Is Your Infrastructure Affected by CVE-2026-92615?

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

Start Free Scan →Browse All CVEs