<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 06:23:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92615 — Flightctl: flightctl: package-global go-git https transport mutated per-repo -- cross-tenant tls-config bleed</title>
      <link>https://db.gcve.eu/vuln/cve-2026-92615</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat Edge Manager 1&lt;/p&gt;
&lt;p&gt;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&amp;#39;s process-global client.Protocols map via gitclient.InstallProtocol(&amp;#34;https&amp;#34;, ...). Because the worker renders devices for multiple organizations concurrently from a shared goroutine pool, whichever tenant&amp;#39;s repository configuration is written last wins for all in-flight git.Clone calls. 
This race condition can cause one tenant&amp;#39;s TLS settings, including InsecureSkipVerify or mTLS client credentials, to leak into another tenant&amp;#39;s git operations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat Edge Manager 1&lt;/p&gt;
&lt;p&gt;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&amp;#39;s process-global client.Protocols map via gitclient.InstallProtocol(&amp;#34;https&amp;#34;, ...). Because the worker renders devices for multiple organizations concurrently from a shared goroutine pool, whichever tenant&amp;#39;s repository configuration is written last wins for all in-flight git.Clone calls. 
This race condition can cause one tenant&amp;#39;s TLS settings, including InsecureSkipVerify or mTLS client credentials, to leak into another tenant&amp;#39;s git operations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-92615</guid>
    </item>
  </channel>
</rss>
