<?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>Fri, 02 Oct 2026 23:59:46 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:4083 — Important: git security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:4083</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: git, AlmaLinux:9: git-all, AlmaLinux:9: git-core, AlmaLinux:9: git-core-doc, AlmaLinux:9: git-credential-libsecret, AlmaLinux:9: git-daemon, AlmaLinux:9: git-email, AlmaLinux:9: git-gui, AlmaLinux:9: git-instaweb, AlmaLinux:9: git-subtree and 5 more&lt;/p&gt;
&lt;p&gt;Git is a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is an exact copy with complete revision history. This not only allows the user to work on and contribute to projects without the need to have permission to push the changes to their official repositories, but also makes it possible for the user to work with no network connection.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* git: Recursive clones RCE (CVE-2024-32002)
* git: RCE while cloning local repos (CVE-2024-32004)
* git: additional local RCE (CVE-2024-32465)
* git: insecure hardlinks (CVE-2024-32020)
* git: symlink bypass (CVE-2024-32021)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: git, AlmaLinux:9: git-all, AlmaLinux:9: git-core, AlmaLinux:9: git-core-doc, AlmaLinux:9: git-credential-libsecret, AlmaLinux:9: git-daemon, AlmaLinux:9: git-email, AlmaLinux:9: git-gui, AlmaLinux:9: git-instaweb, AlmaLinux:9: git-subtree and 5 more&lt;/p&gt;
&lt;p&gt;Git is a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is an exact copy with complete revision history. This not only allows the user to work on and contribute to projects without the need to have permission to push the changes to their official repositories, but also makes it possible for the user to work with no network connection.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* git: Recursive clones RCE (CVE-2024-32002)
* git: RCE while cloning local repos (CVE-2024-32004)
* git: additional local RCE (CVE-2024-32465)
* git: insecure hardlinks (CVE-2024-32020)
* git: symlink bypass (CVE-2024-32021)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:4083</guid>
    </item>
    <item>
      <title>bdu:2024-04214</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04214</link>
      <description>bdu:2024-04214</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04214</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-32020</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-32020</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: git, Alpaquita:stream: git&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: git, Alpaquita:stream: git&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-32020</guid>
    </item>
    <item>
      <title>BIT-git-2024-32020 — Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at…</title>
      <link>https://cve.radiocsirt.org/vuln/bit-git-2024-32020</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: git&lt;/p&gt;
&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: git&lt;/p&gt;
&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-git-2024-32020</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0646 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0646</link>
      <description>certfr-2024-avi-0646</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0646</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-MV02449 — Git is a revision control system</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-mv02449</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. Git is a revision control system.&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. Git is a revision control system.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-mv02449</guid>
    </item>
    <item>
      <title>EUVD-2026-217401</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-217401</link>
      <description>EUVD-2026-217401</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-217401</guid>
    </item>
    <item>
      <title>fkie_cve-2024-32020</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-32020</link>
      <description>&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-32020</guid>
    </item>
    <item>
      <title>gsd-2024-32020</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-32020</link>
      <description>gsd-2024-32020</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-32020</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-32020 — Cloning local Git repository by untrusted user allows the untrusted user to modify objects in the cloned repository at…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-32020</link>
      <description>msrc_CVE-2024-32020</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-32020</guid>
    </item>
    <item>
      <title>OESA-2024-1662 — git security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1662</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: git, openEuler:20.03-LTS-SP4: git, openEuler:22.03-LTS: git, openEuler:22.03-LTS-SP1: git, openEuler:22.03-LTS-SP2: git, openEuler:22.03-LTS-SP3: git&lt;/p&gt;
&lt;p&gt;Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.&#13;
&#13;
Security Fix(es):&#13;
&#13;
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule&amp;amp;apos;s worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won&amp;amp;apos;t work. As always, it is best to avoid cloning repositories from untrusted sources.(CVE-2024-32002)&#13;
&#13;
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in ver…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: git, openEuler:20.03-LTS-SP4: git, openEuler:22.03-LTS: git, openEuler:22.03-LTS-SP1: git, openEuler:22.03-LTS-SP2: git, openEuler:22.03-LTS-SP3: git&lt;/p&gt;
&lt;p&gt;Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.&#13;
&#13;
Security Fix(es):&#13;
&#13;
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule&amp;amp;apos;s worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won&amp;amp;apos;t work. As always, it is best to avoid cloning repositories from untrusted sources.(CVE-2024-32002)&#13;
&#13;
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in ver…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1662</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13968-1 — git-2.45.1-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13968-1</link>
      <description>&lt;p&gt;git-2.45.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;git-2.45.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13968-1</guid>
    </item>
    <item>
      <title>RHSA-2024:4368 — Red Hat Security Advisory: git security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:4368</link>
      <description>&lt;p&gt;git: Recursive clones RCE git: RCE while cloning local repos git: insecure hardlinks git: symlink bypass git: additional local RCE&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;git: Recursive clones RCE git: RCE while cloning local repos git: insecure hardlinks git: symlink bypass git: additional local RCE&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:4368</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1807-2 — Security update for git</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1807-2</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-2024:1807-2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-32020</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-32020</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: git, Ubuntu:20.04:LTS: git, Ubuntu:22.04:LTS: git, Ubuntu:24.04:LTS: git&lt;/p&gt;
&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: git, Ubuntu:20.04:LTS: git, Ubuntu:22.04:LTS: git, Ubuntu:24.04:LTS: git&lt;/p&gt;
&lt;p&gt;Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository&amp;#39;s object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a &amp;#34;proper&amp;#34; clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-32020</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1125 — git: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1125</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer oder ein lokaler authentifizierter Angreiferkann mehrere Schwachstellen in git ausnutzen, um beliebigen Programmcode auszuführen und und die Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer oder ein lokaler authentifizierter Angreiferkann mehrere Schwachstellen in git ausnutzen, um beliebigen Programmcode auszuführen und und die Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1125</guid>
    </item>
  </channel>
</rss>
