CVE-2026-105802: Git LFS may execute arbitrary commands via crafted Git configurations
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.
Published Nov 20, 2026
Affected packages
github.com/git-lfs/git-lfs
- Ecosystem
- Go
- Affected
- >= 0.6.0, <= 2.13.3
- Fixed in
- No patched version yet
- Check
go list -m github.com/git-lfs/git-lfs
github.com/git-lfs/git-lfs/v3
- Ecosystem
- Go
- Affected
- >= 3.0.0, < 3.8.1
- Fixed in
- 3.8.1
- Check
go list -m github.com/git-lfs/git-lfs/v3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to izzysec.
References
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-xrgv-7vx6-5vx6
- https://nvd.nist.gov/vuln/detail/CVE-2026-105802
- https://github.com/git-lfs/git-lfs/commit/1b2672aaa29016e8004369df1406d2a73057f45f
- https://github.com/git-lfs/git-lfs/commit/39b73aa4db821fea6f0da8320128e5e1b919942d
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
- https://github.com/advisories/GHSA-xrgv-7vx6-5vx6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-105803
Git LFS may execute arbitrary commands via crafted Git LFS configurations
high8.6No fixNov 20, 2026CVE-2026-69260
Git LFS may attempt arbitrary remote commands via crafted SSH URLs
high7.6No fixNov 20, 2026CVE-2026-69261
Git LFS may leak HTTP headers after redirections
high7.6No fixNov 20, 2026CVE-2025-26625
Git LFS may write to arbitrary files via crafted symlinks
high8.6Oct 17, 2025CVE-2024-53263
Git LFS permits exfiltration of credentials via crafted HTTP URLs
high8.5No fixJan 14, 2025
