Skip to content
Fencer Vulns
high 7.2

CVE-2021-21237 json

Git LFS can execute a Git binary from the current directory on Windows

published 2021-01-15 5 y ago modified 2026-09-08 2 mo ago also BIT-git-lfs-2021-21237 , EUVD-2022-0965 , GHSA-cx3w-xqmc-84g5 , GO-2021-0098

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

Git LFS is a command line extension for managing large files with Git. On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. This is the result of an incomplete fix for CVE-2020-27955. This issue occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator. Other than avoiding untrusted repositories or using a different operating system, there is no workaround. This is fixed in v2.13.2.

Patch / fix

  • go github.com/git-lfs/git-lfs 1.5.1-0.20210113180018-fc664697ed2c, 2.13.2
  • bitnami git-lfs 2.13.2
  • git_large_file_storage_project git_large_file_storage 2.13.2

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
GitHub 3.1 7.2 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/git-lfs/git-lfs
<2.13.2
<1.5.1-0.20210113180018-fc664697ed2c
2.13.2
1.5.1-0.20210113180018-fc664697ed2c
bitnami git-lfs
<2.13.2
2.13.2

Affected products

  • git-lfs git-lfs

Classification

Weakness
  • CWE-426 Untrusted Search Path
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.