Git LFS may execute arbitrary commands via crafted Git configurations
Published 20 Nov 2026 · Updated 20 Nov 2026
Is your project on an affected github.com/git-lfs/git-lfs?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=0.6.0 <=2.13.3
- Fixed in
- No fix released
- Affected
- >=3.0.0 <3.8.1
- Fixed in
- 3.8.1
go get github.com/git-lfs/git-lfs/v3@v3.8.1Details
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.
Is GHSA-xrgv-7vx6-5vx6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/git-lfs/git-lfs, and gives you the command that fixes it.
More advisories for github.com/git-lfs/git-lfs
- HighCVE-2026-105803Git LFS may execute arbitrary commands via crafted Git LFS configurations · 20 Nov 2026
- HighCVE-2026-69261Git LFS may leak HTTP headers after redirections · 20 Nov 2026
- HighCVE-2026-69260Git LFS may attempt arbitrary remote commands via crafted SSH URLs · 20 Nov 2026
- LowCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks in github.com/git-lfs/git-lfs · 30 Oct 2025
- HighCVE-2025-26625Git LFS may write to arbitrary files via crafted symlinks · 17 Oct 2025
- LowCVE-2024-53263Git LFS permits exfiltration of credentials via crafted HTTP URLs in github.com/git-lfs/git-lfs · 15 Jan 2025
References
- Linkgithub.com/git-lfs/git-lfs/security/advisories/GHSA-xrgv-7vx6-5vx6
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-105802
- Linkgithub.com/git-lfs/git-lfs/commit/1b2672aaa29016e8004369df1406d2a73057f45f
- Linkgithub.com/git-lfs/git-lfs/commit/39b73aa4db821fea6f0da8320128e5e1b919942d
- Packagegithub.com/git-lfs/git-lfs
- Linkgithub.com/git-lfs/git-lfs/releases/tag/v3.8.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.