Git LFS may execute arbitrary commands via crafted Git configurations
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.
References
- github.com/
git-lfs/ git-lfs/ security/ advisories/ GHSA-xrgv-7vx6-5vx6 - nvd.nist.gov/
vuln/ detail/ CVE-2026-105802 - cve.mitre.org/
cgi-bin/ cvename.cgi?name=CVE-2026-105802 - github.com/
git-lfs/ git-lfs/ releases/ tag/ v3.8.1 - git-lfs/git-lfs@39b73aa4db
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.