CVE-2026-92615
A flaw was found in flightctl. The configureRepoHTTPSClient() …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-92615
- bugzilla.redhat.com/show_bug.cgi?id=2518323
- access.redhat.com/errata/RHSA-2026:94632
- access.redhat.com/errata/RHSA-2026:94608
- access.redhat.com/errata/RHSA-2026:94612
- access.redhat.com/errata/RHSA-2026:96291
- access.redhat.com/errata/RHSA-2026:96293
- nvd.nist.gov/vuln/detail/CVE-2026-92615
- cve.org/CVERecord?id=CVE-2026-92615
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.