CVE-2021-21300

HIGHNVD 8.09.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 8.0 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 4 sources updated this weekWeaponized
8.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
CISA-KEV: Not listedEPSS: 89%CVSS: 8.0Exploit: NoneExposed: 0

A fix is available — apply it.

Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive file system such as NTFS, HFS+ or APFS (i.e. the default file systems on Windows and macOS). Note that clean/smudge filters have to be configured for that. Git for Windows configures Git LFS by default, and is therefore vulnerable. The problem has been patched in the versions published on Tuesday, March 9th, 2021. As a workaound, if symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. Likewise, if no clean/smudge filters such as Git LFS are configured globally (i.e. _before_ cloning), the attack is foiled. As always, it is best to avoid cloning repositories from untrusted sources. The earliest impacted version is 2.14.2. The fix versions are: 2.30.1, 2.29.3, 2.28.1, 2.27.1, 2.26.3, 2.25.5, 2.24.4, 2.23.4, 2.22.5, 2.21.4, 2.20.5, 2.19.6, 2.18.5, 2.17.62.17.6.

CVSS v3
8.0
EG Score
9.0(high)
EG Risk
80(Track)
EG Risk 80/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.8%
KEV
Not listed

Published

March 9, 2021

Last Modified

November 21, 2024

References (28)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.7.4-0ubuntu1.10) @ xenial2026-05-26ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:57 UTCEG score recompute
  2. 2026-07-22 21:28 UTCEG score recompute▲ 1.00
  3. 2026-07-22 21:28 UTCVendor advisory
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 00:59 UTCOSV refresh
  7. 2026-07-18 10:02 UTCEPSS rescore
  8. 2026-07-15 16:55 UTCEPSS rescore
  9. 2026-07-15 16:55 UTCEPSS rescore
  10. 2026-07-13 06:10 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-11 08:25 UTCEPSS rescore
  13. 2026-07-09 19:07 UTCEPSS rescore
  14. 2026-07-05 02:28 UTCEPSS rescore
  15. 2026-07-05 02:28 UTCEPSS rescore
  16. 2026-07-01 07:48 UTCOSV refresh
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-15 17:46 UTCEPSS rescore
Show 29 more
  1. 2026-06-13 22:58 UTCEPSS rescore
  2. 2026-06-13 12:13 UTCOSV refresh
  3. 2026-06-12 23:10 UTCEPSS rescore
  4. 2026-06-12 23:10 UTCEPSS rescore
  5. 2026-06-11 13:58 UTCEPSS rescore
  6. 2026-06-10 22:16 UTCEPSS rescore
  7. 2026-06-10 22:16 UTCEPSS rescore
  8. 2026-06-10 13:20 UTCEPSS rescore
  9. 2026-06-08 14:15 UTCEPSS rescore
  10. 2026-06-08 14:15 UTCEPSS rescore
  11. 2026-06-06 13:46 UTCEPSS rescore
  12. 2026-06-06 13:46 UTCEPSS rescore
  13. 2026-06-06 13:46 UTCEPSS rescore
  14. 2026-06-05 22:45 UTCEPSS rescore
  15. 2026-06-05 22:45 UTCEPSS rescore
  16. 2026-06-05 06:09 UTCEPSS rescore
  17. 2026-06-05 06:09 UTCEPSS rescore
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-02 20:11 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-01 13:50 UTCEPSS rescore
  22. 2026-06-01 13:50 UTCEPSS rescore
  23. 2026-05-31 00:15 UTCEPSS rescore
  24. 2026-05-31 00:15 UTCEPSS rescore
  25. 2026-05-29 13:42 UTCEPSS rescore
  26. 2026-05-27 13:39 UTCEPSS rescore
  27. 2026-05-26 20:00 UTCEG score recompute
  28. 2026-05-26 20:00 UTCVendor advisory
  29. 2026-05-24 16:49 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/multi/http/git_lfs_clone_command_exec✓ verified
    First seen Apr 26, 2021

    Git LFS Clone Command Exec

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-21300?
CVE-2021-21300 is a high vulnerability published on March 9, 2021. Git is an open-source distributed revision control system. In affected versions of Git a specially crafted repository that contains symbolic links as well as files using a clean/smudge filter such as Git LFS, may cause just-checked out script to be executed while cloning onto a case-insensitive…
When was CVE-2021-21300 disclosed?
CVE-2021-21300 was first published in the National Vulnerability Database on March 9, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-21300 actively exploited?
CVE-2021-21300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-21300?
CVE-2021-21300 has a CVSS v3 base score of 8.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2021-21300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-21300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-21300

Explore →

Is Your Infrastructure Affected by CVE-2021-21300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs