CVE-2026-105802 — git-lfs
Fix: git-lfs/git-lfs@1b2672aCVE-2026-105802 is a CWE-144 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 execute arbitrary commands via crafted Git configurations
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/git-lfs/git-lfs🐹github.com/git-lfs/git-lfs/v3Real-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 fetching objects from a malicious repository, Git LFS may execute an arbitrary command or binary after incorrectly parsing the Git configuration options defined for a submodule.
Git LFS reads Git configuration options without checking for embedded line-ending control characters. By inserting control characters such as line feed (LF) into certain values, an attacker may be able to mimic options that cause Git LFS to execute an arbitrary command when fetching or adding objects.
Git LFS has resolved this issue by always using an unambiguous format to read and parse Git configuration options.
Patches
This problem exists in all versions since 0.6.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.
Workarounds
To work around the problem, users should prevent Git from initializing any submodules by disabling the fetch.recurseSubmodules and submodule.recurse configuration options and by never running the git submodule init command. Any submodules which have already been initialized in a repository may be deactivated with the git submodule deinit command.
For more information
If you have 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.6.0 | No fix |
| 🐹Go | github.com/git-lfs/git-lfs/v3 | ≥ 3.0.0&&< 3.8.1 | 3.8.1go get github.com/git-lfs/git-lfs/v3@v3.8.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
A fix is available for CVE-2026-105802; check the affected-versions list above or the advisory for the patched release of github.com/git-lfs/git-lfs, then make sure no transitive dependency still pins the vulnerable range.
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.
Frequently Asked Questions
Is CVE-2026-105802 in your dependencies?
Find it across Go, including transitive dependencies.