This update for git-lfs fixes the following issues:
Changes in git-lfs:
update to 3.7.1: (boo#1252259 CVE-2025-26625)
This release introduces security fixes for Linux, macOS, and Windows systems, which have been collectively assigned CVE-2025-26625.
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.
We would like to extend a special thanks to the following open-source contributors: Apple Product Security for reporting this to us responsibly
update to 3.7.0
This release is a feature release which introduces several new options for fetching Git LFS objects, such as the ability to force objects to be re-downloaded and the capacity to output object URLs and HTTP metadata in JSON for external tools to consume. This release also adds a configurable in-memory cache of file path pattern matches, which along with other changes can help reduce the time required to migrate large repositories to Git LFS.
Git LFS now supports the same .netrc files on Windows as Git and curl, retries appropriately after all 429 status code HTTP responses, permits the use of symbolic links to Git's object storage during Git LFS migrations