How severe is CVE-2021-21237?

CVE-2021-21237 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2021-21237 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2021-21237?

CVE-2021-21237 affects Git Large File Storage Project Git Large File Storage. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2021-21237?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2021-21237 published?

CVE-2021-21237 was published on 2021-01-15 and last updated on 2026-06-17.

CVE-2021-21237

CVE-2021-21237 is a high-severity vulnerability in Git Large File Storage Project Git Large File Storage with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-426.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v2: 4.6
EPSS exploit prediction: 0% (35th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-426
Affected product: Git Large File Storage Project Git Large File Storage
Published: 2021-01-15
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2021-21237?: 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.
How severe is CVE-2021-21237?: CVE-2021-21237 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2021-21237 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-21237?: CVE-2021-21237 affects Git Large File Storage Project Git Large File Storage. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2021-21237?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2021-21237 published?: CVE-2021-21237 was published on 2021-01-15 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:git_large_file_storage_project:git_large_file_storage:*:*:*:*:*:*:*:*

More vulnerabilities in Git Large File Storage Project Git Large File Storage

CVE-2022-24826 — Critical (CVSS 9.8): On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and…
CVE-2020-27955 — Critical (CVSS 9.8): Git LFS 2.12.0 allows Remote Code Execution.
CVE-2017-17831 — High (CVSS 8.8): GitHub Git LFS before 2.1.1 allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash…

All CVEs affecting Git Large File Storage Project Git Large File Storage →

Other CWE-426 (Untrusted Search Path) vulnerabilities

CVE-2026-45772 — Critical (CVSS 9.8): Turborepo is a high-performance build system for JavaScript and TypeScript codebases. From 1.1.0 to before 2.9.14,…
CVE-2025-26155 — Critical (CVSS 9.8): NCP Secure Enterprise Client 13.18 and NCP Secure Entry Windows Client 13.19 have an Untrusted Search Path…
CVE-2024-53866 — Critical (CVSS 9.8): The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one…
CVE-2024-38462 — Critical (CVSS 9.8): iRODS before 4.3.2 provides an msiSendMail function with a problematic dependency on the mail binary, such as in the…
CVE-2023-30330 — Critical (CVSS 9.8): SoftExpert (SE) Excellence Suite 2.x versions before 2.1.3 is vulnerable to Local File Inclusion in the function…
CVE-2022-24826 — Critical (CVSS 9.8): On Windows, if Git LFS operates on a malicious repository with a `..exe` file as well as a file named `git.exe`, and…

Browse all CWE-426 (Untrusted Search Path) vulnerabilities →