HighGHSA-6pvw-g552-53c5BIT-git-lfs-2025-26625CVE-2025-26625GO-2025-4038

Git LFS may write to arbitrary files via crafted symlinks

Published 17 Oct 2025 · Updated 31 May 2026

Is your project on an affected github.com/git-lfs/git-lfs?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=0.5.2 <3.7.1
Fixed in
3.7.1
Update to the fixed version for your release line, for example:go get github.com/git-lfs/git-lfs@v3.7.1

Details

Impact

When populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS.

Git LFS has resolved this problem by revising the git lfs checkout and git lfs pull commands so that they check for symbolic links in the same manner as performed by Git before writing to files in the working tree. These commands now also remove existing files in the working tree before writing new files in their place.

As well, Git LFS has resolved a problem whereby the git lfs checkout and git lfs pull commands, when run in a bare repository, could write to files visible outside the repository. While a specific and relatively unlikely set of conditions were required for this to occur, it is no longer possible under any circumstances.

Patches

This problem exists in all versions since 0.5.2 and is patched in v3.7.1. All users should upgrade to v3.7.1.

Workarounds

Support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.

References

For more information

If there are any questions or comments about this advisory:

Is GHSA-6pvw-g552-53c5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/git-lfs/git-lfs, and gives you the command that fixes it.

More advisories for github.com/git-lfs/git-lfs

  • LowCVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs in github.com/git-lfs/git-lfs · 15 Jan 2025
  • HighCVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs · 14 Jan 2025
  • HighCVE-2017-17831GitHub Git LFS Arbitrary command execution vulnerability · 14 May 2022
  • CriticalCVE-2022-24826Git LFS can execute a binary from the current directory on Windows · 22 Apr 2022
  • HighCVE-2021-21237Git LFS can execute a Git binary from the current directory on Windows · 15 Feb 2022
  • CriticalCVE-2020-27955Git LFS can execute a Git binary from the current directory · 11 Feb 2022
All 9 advisories for github.com/git-lfs/git-lfs

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.