flightctl. The configureRepoHTTPSClient() function · CWE-413
Source GCVE Database
Not known to be exploited · CVSS 6.6 Medium : update RHEM 1.2 for RHEL 10 when convenient.
Data as of 3 Nov 2026, 22:58 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.6 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RHEM 1.2 for RHEL 10flightctl | Affected– | Fixed in– |
| RHEM 1.2 for RHEL 9flightctl | Affected– | Fixed in– |
| Red Hat Advanced Cluster Management for Kubernetes 2flightctl | Affected– | Fixed in– |
Description
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.