Git LFS up to 3.7.0 link following

Summaryinfo

A vulnerability, which was classified as critical, was found in Git LFS up to 3.7.0. Affected is an unknown function. The manipulation results in link following. This vulnerability is reported as CVE-2025-26625. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Git LFS up to 3.7.0. Affected is some unknown functionality. The manipulation with an unknown input leads to a link following vulnerability. CWE is classifying the issue as CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, 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. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, 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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-26625 since 02/12/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 271684 (Linux Distros Unpatched Vulnerability : CVE-2025-26625), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.7.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (271684), EUVD (EUVD-2025-34886) and CERT Bund (WID-SEC-2025-2886). Once again VulDB remains the best source for vulnerability data.

Affected

• Red Hat Enterprise Linux
• Oracle Linux
• SUSE openSUSE
• RESF Rocky Linux

Productinfo

Type

• Versioning Software

Name

• Git LFS

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion