<?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>Sun, 18 Oct 2026 14:27:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2025-23390</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2025-23390</link>
      <description>&lt;p&gt;A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2025-23390</guid>
    </item>
    <item>
      <title>GHSA-xgpc-q899-67p8 — Fleet doesn’t validate a server’s certificate when connecting through SSH</title>
      <link>https://db.gcve.eu/vuln/ghsa-xgpc-q899-67p8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/fleet&lt;/p&gt;
&lt;p&gt;### Impact
A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.&lt;/p&gt;
&lt;p&gt;Please consult the associated  [MITRE ATT&amp;amp;CK - Technique - Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557/) for further information about this category of attack.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions include releases `v0.10.12`, `v0.11.7` and `v0.12.2`.&lt;/p&gt;
&lt;p&gt;The fix involves some key areas with the following changes:&lt;/p&gt;
&lt;p&gt;- Git latest commit fetcher sources `known_hosts` entries from the following locations, in decreasing order of priority:
  1. Secret referenced in a `GitRepo`’s `clientSecretName` field;
  2. If no secret is referenced, in a `gitcredential` secret located in the `GitRepo`’s namespace;
  3. If that secret does not exist, in a (new) `known-hosts` config map installed by Fleet, populated statically with public entries shared by a few git providers: Github, Gitlab, Bitbucket, Azure DevOps;&lt;/p&gt;
&lt;p&gt;- Git cloner: same as above.&lt;/p&gt;
&lt;p&gt;- `fleet apply` command: same as above. The command reads entries from a `FLEET_KNOWN_HOSTS` environment variable. That command is typically run within a container insid…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/fleet&lt;/p&gt;
&lt;p&gt;### Impact
A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.&lt;/p&gt;
&lt;p&gt;Please consult the associated  [MITRE ATT&amp;amp;CK - Technique - Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557/) for further information about this category of attack.&lt;/p&gt;
&lt;p&gt;### Patches
Patched versions include releases `v0.10.12`, `v0.11.7` and `v0.12.2`.&lt;/p&gt;
&lt;p&gt;The fix involves some key areas with the following changes:&lt;/p&gt;
&lt;p&gt;- Git latest commit fetcher sources `known_hosts` entries from the following locations, in decreasing order of priority:
  1. Secret referenced in a `GitRepo`’s `clientSecretName` field;
  2. If no secret is referenced, in a `gitcredential` secret located in the `GitRepo`’s namespace;
  3. If that secret does not exist, in a (new) `known-hosts` config map installed by Fleet, populated statically with public entries shared by a few git providers: Github, Gitlab, Bitbucket, Azure DevOps;&lt;/p&gt;
&lt;p&gt;- Git cloner: same as above.&lt;/p&gt;
&lt;p&gt;- `fleet apply` command: same as above. The command reads entries from a `FLEET_KNOWN_HOSTS` environment variable. That command is typically run within a container insid…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xgpc-q899-67p8</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:15059-1 — govulncheck-vulndb-0.0.20250506T153719-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2025:15059-1</link>
      <description>&lt;p&gt;govulncheck-vulndb-0.0.20250506T153719-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;govulncheck-vulndb-0.0.20250506T153719-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2025:15059-1</guid>
    </item>
  </channel>
</rss>
