CVE-2026-105803: github.com/git-lfs/git-lfs · Git LFS may execute arbitrary commands via crafted Git LFS configurations
Affects github.com/git-lfs/git-lfsSource GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 3.8.1 soon.
Data as of 20 Nov 2026, 16:23 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.6 |
|---|
- Patch
- Available – fixed in 3.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade github.com/git-lfs/git-lfs/v3 to 3.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/git-lfs/git-lfs | Affected
| Fixed in– |
| Gogithub.com/git-lfs/git-lfs/v3 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Git LFS to version 3.8.1 or later, where this vulnerability is fixed. Avoid cloning or fetching from untrusted repositories to reduce exposure. There is no effective workaround other than disabling Git LFS entirely, which may not be practical for all users.
Description
Git LFS versions from 1.3.0 up to 2.13.3 and from 3.0.0 up to 3.8.0 contain a vulnerability where crafted .lfsconfig files in malicious repositories can cause Git LFS to execute arbitrary commands. This occurs because Git LFS does not properly restrict configuration options in .lfsconfig files, allowing attackers to specify custom commands for object transfer. The issue is fixed in version 3.8.1. Users should upgrade to this version and avoid cloning repositories from untrusted sources. No effective workaround exists other than disabling Git LFS.
References
- github.com/git-lfs/git-lfs/security/advisories/GHSA-x72p-hmqp-46hw (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-105803 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/1ecddd431e63c551ae11c153df0e07f37d2b44ef (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/45c0c51c8a2d41a7d361b79f3d37f4fec46acc68 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/5182fdeccb834ed887746a557d0c736013704f39 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/62a727e7af1b0de0237c4d288ec0e977613df064 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/c5b3bff4e863022057557ad4be2ce5b5922b1a84 (opens in a new tab)
- github.com/git-lfs/git-lfs/commit/dcfb09ff56eec5825f3e95dbefbfdd520ec76d44 (opens in a new tab)
- github.com/git-lfs/git-lfs (opens in a new tab)
- github.com/git-lfs/git-lfs/releases/tag/v3.8.1 (opens in a new tab)