Vulnerability in github.com/git-lfs/git-lfs (CVE-2025-26625)
Summary
Vulnerability in github.com/git-lfs/git-lfs (CVE-2025-26625). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.7.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-26625 has been found in github.com/git-lfs/git-lfs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/git-lfs/git-lfs to 3.7.1 or later.
If unsure, ask your IT team or search "github.com/git-lfs/git-lfs CVE-2025-26625" on the vendor's site.
CVE-2025-26625 (github.com/git-lfs/git-lfs) — CWE-59
Patched: 3.7.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in github.com/git-lfs/git-lfs.
Check the vendor advisory for the affected versions of github.com/git-lfs/git-lfs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.7.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/git-lfs/git-lfs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/git-lfs/git-lfs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/git-lfs/git-lfsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/git-lfs/git-lfs to 3.7.1ステージング環境で 3.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-26625 git-lfs Fixed in: 2.13.2-1+deb11u2
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web lists.debian.org
- web cve.mitre.org
- web github.com