CVE-2025-26625 — git-lfs
Fix: git-lfs/git-lfs@0cffe93CVE-2025-26625 is a security vulnerability in github.com/git-lfs/git-lfs. A fix is available for github.com/git-lfs/git-lfs — see the affected versions and patch details below.
Git LFS may write to arbitrary files via crafted symlinks
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-26625.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/git-lfs/git-lfsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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.
Patches
This problem exists in all versions since 0.5.2 and is patched in v3.7.1. All users should upgrade to v3.7.1.
Workarounds
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.
References
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-6pvw-g552-53c5
- https://nvd.nist.gov/vuln/detail/CVE-2025-26625
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-26625
- https://github.com/git-lfs/git-lfs/releases/tag/v3.7.1
- git-lfs/git-lfs@5c11ffce9a
- git-lfs/git-lfs@0cffe93176
- git-lfs/git-lfs@d02bd13f02
For more information
If there are any questions or comments about this advisory:
- For general questions, start a discussion in the Git LFS discussion forum.
- For reports of additional vulnerabilities, please follow the Git LFS security reporting policy.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/git-lfs/git-lfs | ≥ 0.5.2&&< 3.7.1 | 3.7.1go get github.com/git-lfs/git-lfs@v3.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/git-lfs/git-lfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/git-lfs/git-lfs to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-26625 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-26625 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-26625. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability can cause Git LFS to write to arbitrary file system locations accessible to the user running git lfs checkout and git lfs pull. These commands are typically run by regular users without special access to system files, limiting the impact of this issue.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | git-lfs-0:3.6.1-4.el10_1 | RHSA-2025:23667 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | ruby-0:3.3.10-11.el10_0 | RHSA-2025:23927 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | git-lfs-0:3.6.1-2.el10_0.1 | RHSA-2026:0224 |
| Red Hat Enterprise Linux 8 | git-lfs-0:3.4.1-6.el8_10 | RHSA-2025:23745 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_4.3 | RHSA-2026:0459 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | git-lfs-0:2.13.3-3.el8_6.5 | RHSA-2026:0465 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | git-lfs-0:3.2.0-2.el8_8.5 | RHSA-2026:0460 |
| Red Hat Enterprise Linux 9 | git-lfs-0:3.6.1-4.el9_7 | RHSA-2025:23744 |
Frequently Asked Questions
Is CVE-2025-26625 in your dependencies?
O3 Security finds CVE-2025-26625 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.