CVE-2026-92615
Flightctl: flightctl: package-global go-git https transport mutated per-repo -- cross-tenant tls-config bleed
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| flightctlRed Hat | unaffected: 0:1.2.2-1.el10 to < * | See vendor advisory |
| flightctlRed Hat | unaffected: 0:1.2.2-1.el9 to < * | See vendor advisory |
| rhem/flightctl-worker-rhel10Red Hat | unaffected: 1793718463 to < * | See vendor advisory |
| rhem/flightctl-worker-rhel9Red Hat | unaffected: 1793718887 to < * | See vendor advisory |
| flightctlRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.