<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 17:44:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2020-01903</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2020-01903</link>
      <description>bdu:2020-01903</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2020-01903</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2020-5260 — CVE-2020-5260 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2020-5260</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2020-5260</guid>
    </item>
    <item>
      <title>BIT-git-2020-5260 — malicious URLs may cause Git to present stored credentials to the wrong server</title>
      <link>https://cve.radiocsirt.org/vuln/bit-git-2020-5260</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: git&lt;/p&gt;
&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: git&lt;/p&gt;
&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-git-2020-5260</guid>
    </item>
    <item>
      <title>certfr-2020-avi-229 — Une vulnérabilité a été découverte dans Apple Xcode. Elle permet à un
attaquant de provoquer une atteinte à la confiden…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2020-avi-229</link>
      <description>certfr-2020-avi-229</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2020-avi-229</guid>
    </item>
    <item>
      <title>CLEANSTART-2025-KZ78895 — Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host con…</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2025-kz78895</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: git&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the git package. Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: git&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the git package. Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2025-kz78895</guid>
    </item>
    <item>
      <title>cnvd-2020-33648</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-33648</link>
      <description>cnvd-2020-33648</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-33648</guid>
    </item>
    <item>
      <title>EUVD-2026-36508</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-36508</link>
      <description>EUVD-2026-36508</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-36508</guid>
    </item>
    <item>
      <title>fkie_cve-2020-5260</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-5260</link>
      <description>&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-5260</guid>
    </item>
    <item>
      <title>gsd-2020-5260</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-5260</link>
      <description>gsd-2020-5260</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-5260</guid>
    </item>
    <item>
      <title>openSUSE-SU-2020:0524-1 — Security update for git</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2020:0524-1</link>
      <description>&lt;p&gt;Security update for git&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for git&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2020:0524-1</guid>
    </item>
    <item>
      <title>RHSA-2020:1503 — Red Hat Security Advisory: rh-git218-git security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2020:1503</link>
      <description>&lt;p&gt;git: Crafted URL containing new lines can cause credential leak&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;git: Crafted URL containing new lines can cause credential leak&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2020:1503</guid>
    </item>
    <item>
      <title>SUSE-SU-2020:0991-1 — Security update for git</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2020:0991-1</link>
      <description>&lt;p&gt;Security update for git&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for git&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2020:0991-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-5260</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-5260</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: git, Ubuntu:18.04:LTS: git&lt;/p&gt;
&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: git, Ubuntu:18.04:LTS: git&lt;/p&gt;
&lt;p&gt;Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. Git uses external &amp;#34;credential helper&amp;#34; programs to store and retrieve passwords or other credentials from secure storage provided by the operating system. Specially-crafted URLs that contain an encoded newline can inject unintended values into the credential helper protocol stream, causing the credential helper to retrieve the password for one server (e.g., good.example.com) for an HTTP request being made to another server (e.g., evil.example.com), resulting in credentials for the former being sent to the latter. There are no restrictions on the relationship between the two, meaning that an attacker can craft a URL that will present stored credentials for any host to a host of their choosing. The vulnerability can be triggered by feeding a malicious URL to git clone. However, the affected URLs look rather suspicious; the likely vector would be through systems which automatically clone URLs not visible to the user, such as Git submodules, or package systems built around Git. The problem has been patched in the versions published on April 14th, 2020, going back to v2.17.x. Anyone wishing to backport the change further can do so by applying commit 9a6bbee (the full release includes extra checks for git fsck, but that commit is sufficient to protect clients against the vulnerability). The patched versions are: 2.17.4, 2.18.3, 2.19.4, 2.20.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-5260</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0189 — git: Schwachstelle ermöglicht Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0189</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in git ausnutzen, um Anmeldeinformationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in git ausnutzen, um Anmeldeinformationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0189</guid>
    </item>
  </channel>
</rss>
