Git LFS may execute arbitrary commands via crafted Git LFS configurations
Description
Impact
When fetching objects from a malicious repository, Git LFS may execute an arbitrary command or binary after failing to sufficiently restrict the set of configuration options defined in an .lfsconfig file in the repository.
Git LFS permits a limited set of configuration options to be defined in an .lfsconfig file at the root of a Git repository, but does not filter these options correctly if their keys contain certain additional components, which allows an attacker to mimic options that configure Git LFS to use a custom command to transfer objects. An attacker can then provide an arbitrary command which Git LFS will invoke when fetching objects.
Git LFS has resolved this issue by correctly restricting the configuration of custom object transfer commands to local Git configuration files.
Patches
This problem exists in all versions since 1.3.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.
Workarounds
No single workaround exists other than to disable Git LFS entirely. As far as possible, users and administrators should avoid cloning repositories from untrusted sources.
References
- github.com/
git-lfs/ git-lfs/ security/ advisories/ GHSA-x72p-hmqp-46hw - nvd.nist.gov/
vuln/ detail/ CVE-2026-105803 - cve.mitre.org/
cgi-bin/ cvename.cgi?name=CVE-2026-105803 - github.com/
git-lfs/ git-lfs/ releases/ tag/ v3.8.1 - git-lfs/git-lfs@62a727e7af
- git-lfs/git-lfs@5182fdeccb
- git-lfs/git-lfs@1ecddd431e
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.