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

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

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-q6r7-r3xg-x977

## 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 (Improper Resource Locking)

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92615 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-92615 in the wild and no public exploit code.

Affected product: Red Hat Advanced Cluster Management for Kubernetes 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92615/ (Markdown: https://insights.sbomify.com/CVE-2026-92615/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92615
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92615
- OSV: https://osv.dev/vulnerability/CVE-2026-92615

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92615/
Summaries are generated and may contain mistakes; the official description above is the record.