Git LFS CVE-2025-26625
HIGHSeverity by source
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:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
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:X/V:X/RE:X/U:X
Lifecycle Timeline
6DescriptionCVE.org
Alpine Linux: git-lfs fixed in 3.7.1-r0
AnalysisAI
Arbitrary file write in Git LFS versions 0.5.2 through 3.7.0 allows a malicious repository to overwrite files outside the working tree when a user runs git lfs checkout or git lfs pull against a repository containing crafted symbolic or hard links that collide with LFS-tracked file paths. The flaw is fixed in v3.7.1 and is also exploitable in bare repositories under specific conditions. No public exploit identified at time of analysis, and EPSS is very low (0.05%), but the CVSS 4.0 score of 8.6 reflects the high integrity impact achievable through routine developer workflows.
Technical ContextAI
Git LFS is a Git extension written in Go that stores large binary files outside the main Git object store and materializes them into the working tree on checkout or pull. The root cause is CWE-59 (Link Following): prior to v3.7.1, the checkout and pull commands wrote LFS object content to target paths without first verifying that intermediate path components were not symbolic links, unlike Git itself which performs explicit symlink checks before writing. The patch (commits 0cffe93, 5c11ffc, d02bd13) introduces a new DirWalker abstraction in the tools package that walks each path component and refuses to traverse symlinks, and removes the unsafe MkdirAll call from lfs/gitfilter_smudge.go that previously created directories without symlink validation. A secondary issue allowed bare repositories to write outside their own directory under narrow conditions, which the same patch eliminates.
Affected ProductsAI
Git LFS versions from 0.5.2 through and including 3.7.0 are vulnerable across all platforms (Linux, macOS, Windows). Distribution packagings are also affected, including Alpine Linux's git-lfs package (fixed in 3.7.1-r0 per the Alpine vendor report) and Debian (with a Debian LTS announcement listed at lists.debian.org/debian-lts-announce/2026/05/msg00055.html). The upstream Go module is github.com/git-lfs/git-lfs, with the vendor advisory at https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5.
RemediationAI
Vendor-released patch: upgrade Git LFS to v3.7.1 or later (https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1); Alpine users should install git-lfs 3.7.1-r0 and Debian users should apply the LTS update referenced at lists.debian.org/debian-lts-announce/2026/05/msg00055.html. If upgrading immediately is not feasible, the vendor suggests setting git config core.symlinks=false so future clones and fetches do not create symbolic links, with the important caveat that any pre-existing symlinks or hard links in already-cloned repositories remain exploitable and this setting also breaks legitimate symlink-based workflows. Additional compensating controls: avoid running git lfs checkout or git lfs pull on untrusted repositories until patched, and audit CI runners and developer workstations to ensure the updated version is installed. The vendor advisory is GHSA-6pvw-g552-53c5.
Same weakness CWE-59 – Improper Link Resolution Before File Access
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
GHSA-6pvw-g552-53c5