CVE-2026-92615 json
Flightctl: flightctl: package-global go-git https transport mutated per-repo -- cross-tenant tls-config bleed
published last mo. modified 7d ago also EUVD-2026-80802
- cvss
- 6.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Red Hat RHEM 1.2 for RHEL 10 0:1.2.2-1.el10
- Red Hat RHEM 1.2 for RHEL 9 0:1.2.2-1.el9
- Red Hat Red Hat Edge Manager 1.2 1793718463, 1793718887
Is CVE-2026-92615 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-92615 updated cvss 6.6
flightctl: flightctl: Package-global go-git HTTPS transport mutated per-repo -- cross-tenant TLS-config bleed
-
Red Hat Advanced Cluster Management for Kubernetes 2 flightctl, flightctl-agent, flightctl-selinuxaffected: workaround, no fix planned “Will not fix”
-
Red Hat Edge Manager 1.2 rhem/flightctl-worker-rhel9 1793718887, rhem/flightctl-worker-rhel10 1793718463fixed: vendor fix RHSA-2026:94612
-
Red Hat RHEM 1.2 for RHEL 9 flightctl 1.2.2-1.el9, flightctl-cli 1.2.2-1.el9, flightctl-agent 1.2.2-1.el9 Red Hat RHEM 1.2 for RHEL 10 flightctl 1.2.2-1.el10, flightctl-cli 1.2.2-1.el10, flightctl-agent 1.2.2-1.el10fixed: vendor fix RHSA-2026:94632
-
Red Hat Edge Manager 1.2 rhem/flightctl-ui-rhel9 1793718718, rhem/flightctl-api-rhel9 1793718545, rhem/flightctl-ui-rhel10 1793720014, rhem/flightctl-api-rhel10 1793719962, rhem/flightctl-ui-ocp-rhel9 1793719442, rhem/flightctl-ui-ocp-rhel10 1793719672, +20 more Red Hat RHEM 1.2 for RHEL 9 flightctl-selinux 1.2.2-1.el9, flightctl-services 1.2.2-1.el9, flightctl-observability 1.2.2-1.el9 Red Hat RHEM 1.2 for RHEL 10 flightctl-selinux 1.2.2-1.el10, flightctl-services 1.2.2-1.el10, flightctl-observability 1.2.2-1.el10not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.6 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N |
Affected products
- Red Hat RHEM 1.2 for RHEL 10
- Red Hat RHEM 1.2 for RHEL 9
- Red Hat Red Hat Edge Manager 1.2
- Red Hat Red Hat Advanced Cluster Management for Kubernetes 2
Classification
- Weakness
-
- CWE-413 Improper Resource Locking
References
-
access.redhat.com
/errata/RHSA-2026:94608
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:94612
vendor-advisory
-
access.redhat.com
/errata/RHSA-2026:94632
vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-92615
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2518323
issue-tracking
Sources
- CVE List CVE-2026-92615
- NVD CVE-2026-92615
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.