CVE-2025-26625

git-lfs: Git LFS is a Git extension for versioning large files

CVE-2025-26625 is fixed in 6 products on 1 platform, first by git-lfs 3.4.1-1ubuntu0.3+esm2, released October 17, 2025. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
8.1
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0106
64th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
git-lfs · Debian 12.15 (bookworm) 3.3.0-1+deb12u2 DEBIAN-CVE-2025-26625 Oct 17, 2025
git-lfs · Debian 13.5 (trixie) 3.6.1-1+deb13u1 DEBIAN-CVE-2025-26625 Oct 17, 2025
git-lfs · Debian 14 3.7.1-1 DEBIAN-CVE-2025-26625 Oct 17, 2025
git-lfs · RHEL 10 3.6.1-2.el10_0.1 RHSA-2026:0224 Oct 17, 2025
git-lfs · RHEL 8 0:3.4.1-6.el8_10 RHSA-2025:23745 Jan 16, 2026
git-lfs · RHEL 9 0:3.6.1-4.el9_7 RHSA-2025:23744 Jan 16, 2026
git-lfs · Ubuntu 24.04.5 LTS (noble) 3.4.1-1ubuntu0.3+esm2 git-lfs 3.4.1-1ubuntu0.3+esm2 Oct 17, 2025
git-lfs · Ubuntu 25.10 (questing) 3.6.1-1ubuntu0.1 git-lfs 3.6.1-1ubuntu0.1 Oct 17, 2025
git-lfs · almalinux 10 3.6.1-4.el10_1 ALSA-2025:23667 Dec 18, 2025
git-lfs · almalinux 8 3.4.1-6.el8_10 ALSA-2025:23745 Dec 22, 2025
git-lfs · almalinux 9 3.6.1-4.el9_7 ALSA-2025:23744 Dec 22, 2025
git-lfs · amzn 2023 3.7.1-79.amzn2023 ALAS2023-2025-1258 Nov 10, 2025
git-lfs · ol 10 0:3.6.1-4.el10_1 ELSA-2025-23667 Dec 18, 2025
git-lfs · ol 8 0:3.4.1-6.el8_10 ELSA-2025-23745 Dec 21, 2025
git-lfs · ol 9 0:3.6.1-4.el9_7 ELSA-2025-23744 Dec 21, 2025
git-lfs · opensuse-leap 16.0 3.7.1-bp160.1.1 OPENSUSE-SU-2026:21621-1 Aug 21, 2026
git-lfs · rocky 10 0:3.6.1-4.el10_1 RLSA-2025:23667 Dec 20, 2025
git-lfs · rocky 8 0:3.4.1-6.el8_10 RLSA-2025:23745 Dec 23, 2025
git-lfs · rocky 9 0:3.6.1-4.el9_7 RLSA-2025:23744 Dec 23, 2025
git-lfs · sles 15.6 3.7.1-150600.13.6.1 SUSE-SU-2026:3801-1 Aug 25, 2026
git-lfs · sles 15.7 3.7.1-150600.13.6.1 SUSE-SU-2026:3801-1 Aug 25, 2026
git-lfs-debuginfo · amzn 2023 3.7.1-79.amzn2023 ALAS2023-2025-1258 Nov 10, 2025
git-lfs-debugsource · amzn 2023 3.7.1-79.amzn2023 ALAS2023-2025-1258 Nov 10, 2025
golang-github-git-lfs-git-lfs-dev · Ubuntu 24.04.5 LTS (noble) 3.4.1-1ubuntu0.3+esm2 golang-github-git-lfs-git-lfs-dev 3.4.1-1ubuntu0.3+esm2 Oct 17, 2025
golang-github-git-lfs-git-lfs-dev · Ubuntu 25.10 (questing) 3.6.1-1ubuntu0.1 golang-github-git-lfs-git-lfs-dev 3.6.1-1ubuntu0.1 Oct 17, 2025
govulncheck-vulndb · opensuse-leap 16.0 0.0.20260723T184607-160000.1.1 OPENSUSE-SU-2026:21483-1 Jul 30, 2026
ruby · RHEL 10 3.3.10-11.el10_0 RHSA-2025:23927 Oct 17, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.