Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.6
CVE-2026-105802: Git LFS can run unwanted commands when fetching
CVE-2026-105802 · published today
Summary
Git LFS may run any command an attacker places in a crafted repository configuration. Upgrade to version 3.8.1 or later, or disable submodule fetching, to stop this behavior.
What to do
- Update debian git-lfs to version 3.8.1-1.
- Update github.com git-lfs to version 3.8.1.
- Update git-lfs github.com/git-lfs/git-lfs/v3 to version 3.8.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | git-lfs | git-lfs | >= 0.6.0, <= 2.13.3 |
| Debian:12 | debian | git-lfs | All versions |
| Debian:14 | debian | git-lfs |
< 3.8.1-1 Fix: upgrade to 3.8.1-1
|
| go | github.com | git-lfs | >= 0.6.0, <= 2.13.3 |
| go | github.com | git-lfs |
>= 3.0.0, < 3.8.1 Fix: upgrade to 3.8.1
|
| Go | git-lfs | github.com/git-lfs/git-lfs | >= 0.6.0, <= 2.13.3 |
| Go | git-lfs | github.com/git-lfs/git-lfs/v3 |
>= 3.0.0, < 3.8.1 Fix: upgrade to 3.8.1
|
Original advisory text
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. 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](https://github.com/git-lfs/git-lfs/discussions).
* For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md).
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](https://github.com/git-lfs/git-lfs/discussions).
* For reports of additional vulnerabilities, please follow the Git LFS [security reporting policy](https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md).
References
- https://github.com/git-lfs/git-lfs/commit/1b2672aaa29016e8004369df1406d2a73057f4...
- https://github.com/git-lfs/git-lfs/commit/39b73aa4db821fea6f0da8320128e5e1b91994...
- https://github.com/git-lfs/git-lfs/security/advisories/GHSA-xrgv-7vx6-5vx6
- https://github.com/git-lfs/git-lfs/releases/tag/v3.8.1
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/105xxx/CVE-2026-1058... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-105802
- https://security-tracker.debian.org/tracker/CVE-2026-105802 Vendor Advisory
- https://github.com/advisories/GHSA-xrgv-7vx6-5vx6
- https://github.com/git-lfs/git-lfs Product
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Type
CWE-144Improper Neutralization of Line Delimiters
Timeline
Published20 Nov 2026
Updated21 Nov 2026
First seen19 Nov 2026
Sources
CVE-2026-105802 · NVD
CVE-2026-105802 · MITRE
CVE-2026-105802 · OSV
GHSA-xrgv-7vx6-5vx6 · GHSA
DEBIAN-CVE-2026-105802 · OSV
GHSA-xrgv-7vx6-5vx6 · OSV
Track software like this
Free during beta