CVE-2024-32021

LOWNVD 3.93.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This low-severity CVE scores 3.9 under NVD CVSS v3. EPSS exploit probability: 1.0% (62nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
3.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 3.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

CVSS v3
3.9
EG Score
3.9LOWmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity39% × 45%
The EG Score, 3.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 14, 2024

Last Modified

January 5, 2026

References (5)

Vendor Advisories for CVE-2024-32021(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugitweb (1:2.43.0-1ubuntu7.1) @ noble2026-05-24ubuntu
ubuntugitweb (1:2.7.4-0ubuntu1.10+esm8) @ xenial2026-05-24ubuntu
redhatgit-0:2.39.5-1.el9_22024-07-08redhat
redhatgit-0:2.43.5-1.el8_102024-06-25redhat
redhatgit-0:2.43.5-1.el9_42024-06-25redhat

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.

Affected Packages

(13 across 13 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.39.5-r0: fixed in 2.39.5-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.40.3-r0: fixed in 2.40.3-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.43.4-r0: fixed in 2.43.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.45.1-r0: fixed in 2.45.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.45.1-r0: fixed in 2.45.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.45.1-r0: fixed in 2.45.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.45.1-r0: fixed in 2.45.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.40.0 up to 2.45.1-r0: fixed in 2.45.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.20.1-2 ... 1:2.20.1-2+deb10u8 (9 versions)
  • every version up to 1:2.20.1-2+deb10u9: fixed in 1:2.20.1-2+deb10u9
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.30.2-1, 1:2.30.2-1+deb11u1, 1:2.30.2-1+deb11u2
  • every version up to 1:2.30.2-1+deb11u3: fixed in 1:2.30.2-1+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.39.2+next.20230215-1, 1:2.39.2-1.1
  • every version up to 1:2.39.5-0+deb12u1: fixed in 1:2.39.5-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.45.1-1: fixed in 1:2.45.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.45.1-1: fixed in 1:2.45.1-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-10-12 17:55 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  6. 2026-10-11 21:20 UTCEG score recompute
  7. 2026-10-11 16:13 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-10-11 01:22 UTCOSV refresh
  10. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-09-30 19:43 UTCEG score recompute
  20. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  23. 2026-09-27 13:43 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  24. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 66 more
  1. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  2. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-09-21 13:19 UTCOSV refresh
  5. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  6. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  7. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  9. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  12. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  15. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  18. 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  21. 2026-09-02 10:44 UTCOSV refresh
  22. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  25. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  26. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  27. 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  28. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  29. 2026-08-24 14:15 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  30. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  31. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  32. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  33. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  34. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  35. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  36. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  37. 2026-08-16 08:52 UTCOSV refresh
  38. 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  39. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  40. 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  41. 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  42. 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  43. 2026-08-10 23:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  44. 2026-08-09 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  45. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  46. 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  47. 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  48. 2026-08-05 19:16 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  49. 2026-08-04 15:08 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  50. 2026-08-04 10:36 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  51. 2026-08-03 10:34 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  52. 2026-08-02 02:25 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  53. 2026-08-01 04:14 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  54. 2026-08-01 03:12 UTCOSV refresh
  55. 2026-07-30 16:26 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  56. 2026-07-30 01:29 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  57. 2026-07-28 15:34 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  58. 2026-07-27 14:11 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  59. 2026-07-26 14:53 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  60. 2026-07-25 14:16 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  61. 2026-07-24 14:16 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  62. 2026-07-23 14:17 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  63. 2026-07-23 02:36 UTCEG score recompute
  64. 2026-07-22 14:07 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  65. 2026-07-21 15:23 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  66. 2026-07-20 17:06 UTCEPSS rescoreEPSS 1.0% · 57th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-32021?
CVE-2024-32021 is a low-severity vulnerability; its CVE record was published on May 14, 2024. Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository…
When was the CVE record for CVE-2024-32021 published?
The CVE record for CVE-2024-32021 was published on May 14, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 5, 2026; the record at its source may have been updated since.
Is CVE-2024-32021 actively exploited?
CVE-2024-32021 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32021?
CVE-2024-32021 has a CVSS v3 base score of 3.9 (NVD).
How do I remediate CVE-2024-32021?
A fix for CVE-2024-32021 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-32021 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32021

Explore →

Is Your Infrastructure Affected by CVE-2024-32021?

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

Book a Demo →Browse All CVEs