CVE-2026-92615 Flightctl: flightctl: package-global go-git https transport mutated per-repo -- cross-tenant tls-config bleed

Medium 6.6 Published Updated

A race condition in flightctl allows cross-tenant leakage of TLS configurations, potentially exposing sensitive credentials or bypassing certificate validation.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-92615?

CVE-2026-92615 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official 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.

Weakness: CWE-413

Which versions are affected by CVE-2026-92615?

How do I fix CVE-2026-92615?

No fix has been published for CVE-2026-92615 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-92615 being exploited?

There is no known exploitation of CVE-2026-92615 in the wild and no public exploit code.

Sources

Also known as GHSA-q6r7-r3xg-x977.

Is CVE-2026-92615 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free