<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-18T05:46:40.011486+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-71557</id>
    <title>CVE-2026-71557 — go-git: Malicious reference names may modify files outside the reference storage</title>
    <updated>2026-11-18T05:46:40.013005+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> go-git</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-71557"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qgq7-7hm3-q39j</id>
    <title>GHSA-qgq7-7hm3-q39j — go-git: Malicious reference names may modify files outside the reference storage</title>
    <updated>2026-11-18T05:46:40.013056+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/go-git/go-git/v5, Go: github.com/go-git/go-git/v6</p>
<p>### Impact
A path traversal issue in `go-git` could allow malicious reference names to access files outside the repository's intended reference storage.</p>
<p>Loose references are stored under `.git/&lt;reference-name&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`.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>### 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.</p>
<p>Users of filesystem-backed storage should upgrade to a patched version.</p>
<p>### Workarounds
Applications that exclusively use `storage/memory` ar…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qgq7-7hm3-q39j"/>
  </entry>
</feed>
