← Vulnerability feed

Vulnerability record · CVE-2025-26625 · published 17 October 2025

CVE-2025-26625: Link following vulnerability

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.

8.6 CVSS 4.0 High EPSS 0.75% · top 47.0% CWE-59 · Link following Deferred
8.6CVSS 4.0 base score
0.75%EPSS exploitation probability, 30 days
NoNot in CISA KEV
0Affected product versions listed by NVD
6References
17 Jun 2026Last modified by NVD

Description

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.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:

References

LinkTags
https://github.com/git-lfs/git-lfs/commit/0cffe93176b870055c9dadbb3cc9a4a440e98396
https://github.com/git-lfs/git-lfs/commit/5c11ffce9a4f095ff356bc781e2a031abb46c1a8
https://github.com/git-lfs/git-lfs/commit/d02bd13f02ef76f6807581cd6b34709069cb3615
https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1
https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5
https://lists.debian.org/debian-lts-announce/2026/05/msg00055.html

Track CVE-2025-26625 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

7.8CVE-2026-81963Windows Update Stack link-following privilege escalationWindows Update Stack resolves links improperly before accessing files, a link-following flaw (CWE-59) compounded by improper access control (CWE-284)…KEVEPSS 0.39%analysed7.8CVE-2015-5287ABRT abrt-hook-ccpp symlink privilege escalationThe abrt-hook-ccpp helper in Red Hat's Automatic Bug Reporting Tool (ABRT) before 2.7.1 follows symlinks on files with predictable names, letting a l…KEVEPSS 5.0%analysed7.8CVE-2026-41091Microsoft Defender link following allows local privilege elevationMicrosoft Defender's malware protection engine resolves links improperly before accessing files, a link-following flaw (CWE-59). A local attacker wit…KEVEPSS 0.44%analysed7.2CVE-2024-57728SimpleHelp zip slip path traversal allows arbitrary file write and code executionSimpleHelp remote support software v5.5.7 and earlier lets admin users upload a crafted zip file that writes files anywhere on the file system via zi…KEVEPSS 65%analysed7.8CVE-2025-60710Windows Task Host link following privilege escalationThe Host Process for Windows Tasks resolves links improperly before accessing files (CWE-59), letting a local attacker redirect file operations to at…KEVEPSS 4.6%analysed8.0CVE-2025-48384Git config CRLF handling allows submodule path link-following code executionGit mishandles trailing carriage returns when writing config values, so a submodule path ending in CR is read back altered during submodule initializ…KEVEPSS 4.1%analysed7.1CVE-2025-21391Microsoft Windows Storage Elevation of Privilege via Link FollowingCVE-2025-21391 is a link-following flaw in the Windows Storage component that lets a local user escalate privileges. It affects a broad set of Window…KEVEPSS 2.3%analysed7.0CVE-2024-38106Windows Kernel elevation of privilege via race conditionCVE-2024-38106 is a Windows Kernel elevation of privilege vulnerability affecting a broad set of Windows 10, Windows 11 and Windows Server releases. …KEVEPSS 6.3%analysed

Source: NIST National Vulnerability Database (record CVE-2025-26625), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.