<?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>Wed, 18 Nov 2026 05:46:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-71557 — go-git: Malicious reference names may modify files outside the reference storage</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-71557</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; go-git&lt;/p&gt;
&lt;p&gt;go-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; go-git&lt;/p&gt;
&lt;p&gt;go-git is an extensible git implementation library written in pure Go. Prior to 5.19.2 and 6.0.0-alpha.5, reference names are not sanitized before being used to construct on-disk paths under the reference storage directory, so a maliciously crafted reference name (for example containing directory-traversal sequences) can cause go-git to write files outside the intended reference storage directory. Versions 5.19.2 and 6.0.0-alpha.5 fix the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-71557</guid>
    </item>
    <item>
      <title>GHSA-qgq7-7hm3-q39j — go-git: Malicious reference names may modify files outside the reference storage</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qgq7-7hm3-q39j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-git/go-git/v5, Go: github.com/go-git/go-git/v6&lt;/p&gt;
&lt;p&gt;### Impact
A path traversal issue in `go-git` could allow malicious reference names to access files outside the repository&amp;#39;s intended reference storage.&lt;/p&gt;
&lt;p&gt;Loose references are stored under `.git/&amp;lt;reference-name&amp;gt;`. The reference name was previously used as a path without verifying that the resolved path remained within the reference storage. A name such as `refs/heads/../../config` could therefore resolve to unrelated repository metadata such as `.git/config` or `.git/HEAD`.&lt;/p&gt;
&lt;p&gt;A malicious Git server could advertise such a reference name. The name may also survive refspec mapping; for example, it could be mapped to `refs/remotes/origin/../../config` during a clone or fetch operation.&lt;/p&gt;
&lt;p&gt;This vulnerability affects filesystem-backed repositories using the `storage/filesystem` package and its `dotgit` reference storage. Users relying exclusively on the in-memory storage implementation, `storage/memory`, are not affected, because reference names are not resolved as filesystem paths.&lt;/p&gt;
&lt;p&gt;Exploitation requires an application using `go-git` with filesystem-backed storage to interact with a malicious Git server or otherwise process attacker-controlled reference names.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been addressed by validating reference names at the `dotgit` storage entry points and rejecting names whose resolved paths could escape the reference storage.&lt;/p&gt;
&lt;p&gt;Users of filesystem-backed storage should upgrade to a patched version.&lt;/p&gt;
&lt;p&gt;### Workarounds
Applications that exclusively use `storage/memory` ar…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/go-git/go-git/v5, Go: github.com/go-git/go-git/v6&lt;/p&gt;
&lt;p&gt;### Impact
A path traversal issue in `go-git` could allow malicious reference names to access files outside the repository&amp;#39;s intended reference storage.&lt;/p&gt;
&lt;p&gt;Loose references are stored under `.git/&amp;lt;reference-name&amp;gt;`. The reference name was previously used as a path without verifying that the resolved path remained within the reference storage. A name such as `refs/heads/../../config` could therefore resolve to unrelated repository metadata such as `.git/config` or `.git/HEAD`.&lt;/p&gt;
&lt;p&gt;A malicious Git server could advertise such a reference name. The name may also survive refspec mapping; for example, it could be mapped to `refs/remotes/origin/../../config` during a clone or fetch operation.&lt;/p&gt;
&lt;p&gt;This vulnerability affects filesystem-backed repositories using the `storage/filesystem` package and its `dotgit` reference storage. Users relying exclusively on the in-memory storage implementation, `storage/memory`, are not affected, because reference names are not resolved as filesystem paths.&lt;/p&gt;
&lt;p&gt;Exploitation requires an application using `go-git` with filesystem-backed storage to interact with a malicious Git server or otherwise process attacker-controlled reference names.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been addressed by validating reference names at the `dotgit` storage entry points and rejecting names whose resolved paths could escape the reference storage.&lt;/p&gt;
&lt;p&gt;Users of filesystem-backed storage should upgrade to a patched version.&lt;/p&gt;
&lt;p&gt;### Workarounds
Applications that exclusively use `storage/memory` ar…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qgq7-7hm3-q39j</guid>
    </item>
  </channel>
</rss>
