How severe is CVE-2021-46101?

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

Is CVE-2021-46101 being actively exploited?

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

What products are affected by CVE-2021-46101?

CVE-2021-46101 affects Gitforwindows Git. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2021-46101?

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-46101 published?

CVE-2021-46101 was published on 2022-01-31 and last updated on 2026-06-17.

CVE-2021-46101

CVE-2021-46101 is a high-severity vulnerability in Gitforwindows Git with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (69th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gitforwindows Git
Published: 2022-01-31
Last modified: 2026-06-17

Description

In Git for windows through 2.34.1 when using git pull to update the local warehouse, git.cmd can be run directly.

Frequently asked questions

What is CVE-2021-46101?: In Git for windows through 2.34.1 when using git pull to update the local warehouse, git.cmd can be run directly.
How severe is CVE-2021-46101?: CVE-2021-46101 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2021-46101 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-46101?: CVE-2021-46101 affects Gitforwindows Git. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2021-46101?: 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-46101 published?: CVE-2021-46101 was published on 2022-01-31 and last updated on 2026-06-17.

References

https://github.com/0xADY/git_rce

Affected products (1)

cpe:2.3:a:gitforwindows:git:*:*:*:*:*:windows:*:*

More vulnerabilities in Gitforwindows Git

CVE-2022-31012 — High (CVSS 8.2): Git for Windows is a fork of Git that contains Windows-specific patches. This vulnerability in versions prior to 2.37.1…
CVE-2018-11235 — High (CVSS 7.8): In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1,…
CVE-2025-66413 — High (CVSS 7.4): Git for Windows is the Windows port of Git. Prior to 2.53.0(2), it is possible to obtain a user's NTLM hash by tricking…

All CVEs affecting Gitforwindows Git →