CVE-2021-46101 json
In Git for windows through 2.34.1 when using git pull to update the local warehouse, git.cmd can be run directly.
published 2022-01-31 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-32802
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
In Git for windows through 2.34.1 when using git pull to update the local warehouse, git.cmd can be run directly.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-46101 updated cvss 7.5
git: git.cmd can be run directly when using git pull to update the local warehouse
-
Red Hat Enterprise Linux 7 git, gitk, git-hg, git-p4, gitweb, git-all, +12 more Red Hat Enterprise Linux 8 git, gitk, gitweb, git-all, git-gui, git-svn, +8 more Red Hat Enterprise Linux 9 git, gitk, gitweb, git-all, git-gui, git-svn, +8 more Red Hat Software Collections rh-git227-git, rh-git227-gitk, rh-git227-git-p4, rh-git227-gitweb, rh-git227-git-all, rh-git227-git-cvs, +10 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/0xADY/git_rce referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
References
-
github.com
/0xADY/git_rce
exploit, third-party-advisory
Sources
- CVE List CVE-2021-46101
- NVD CVE-2021-46101
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.
CPEs and fixed versions use Anchore's correction of NVD's data: unclear if this is real or what the fix may be, for now just align with NVD affected ranges. Not worth wasting resources on further analysis currently.