<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-06T15:25:41.250606+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/ghsa-4g4p-42wc-9f3m</id>
    <title>GHSA-4g4p-42wc-9f3m — Git LFS can execute a Git binary from the current directory</title>
    <updated>2026-11-06T15:25:41.251658+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/git-lfs/git-lfs</p>
<p>### Impact
On Windows, if Git LFS operates on a malicious repository with a `git.bat` or `git.exe` file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code.  This does not affect Unix systems.</p>
<p>This occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator.</p>
<p>### Patches
This version should be patched in v2.12.1, which will be released in coordination with this security advisory.</p>
<p>### Workarounds
Other than avoiding untrusted repositories, there is no workaround.</p>
<p>### For more information
If you have any questions or comments about this advisory:
* Start a discussion in [the Git LFS discussion page](https://github.com/git-lfs/git-lfs/discussions).
* If you cannot open a discussion, please email the core team using their usernames at `github.com`.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-4g4p-42wc-9f3m"/>
  </entry>
</feed>
