CVE-2024-32002

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 80.4%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 25%CVSS: 9.0Exploit: NoneExposed: 0

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, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. 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. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
—
EPSS
97.7%
KEV
Not listed

Published

May 14, 2024

Last Modified

November 4, 2025

References (15)

Vendor Advisories for CVE-2024-32002(2)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.25.1-1ubuntu3.13) @ focal2026-05-24ubuntu
ubuntugitweb (1:2.34.1-1ubuntu1.11) @ jammy2026-05-24ubuntu
ubuntugitweb (1:2.7.4-0ubuntu1.10+esm8) @ xenial2026-05-24ubuntu
redhatgit-0:2.31.1-6.el9_02024-09-11redhat
redhatgit-0:2.31.8-3.el8_62024-08-29redhat
redhatgit-0:2.27.0-5.el8_42024-08-29redhat
redhatgit-0:2.39.5-1.el8_82024-07-16redhat
redhatgit-0:2.39.5-1.el9_22024-07-08redhat
redhatgit-0:2.43.5-1.el9_42024-06-25redhat
redhatgit-0:2.43.5-1.el8_102024-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.

Weakness Classification(3)

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

Additional Vendor Advisories

(9)

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 10× in last 7d / 41× 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-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-20 17:06 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-16 17:01 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-14 10:40 UTCOSV refresh
  14. 2026-07-13 22:28 UTCEPSS rescore
  15. 2026-07-12 05:45 UTCEPSS rescore
  16. 2026-07-11 08:26 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-08 15:13 UTCEPSS rescore
  20. 2026-07-06 16:26 UTCEPSS rescore
  21. 2026-07-06 16:26 UTCEPSS rescore
  22. 2026-07-05 02:29 UTCEPSS rescore
  23. 2026-07-04 06:30 UTCEPSS rescore
  24. 2026-07-02 17:00 UTCEPSS rescore
  25. 2026-07-01 15:05 UTCEPSS rescore
Show 54 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-30 23:21 UTCEPSS rescore
  3. 2026-06-29 14:05 UTCEPSS rescore
  4. 2026-06-28 14:06 UTCEPSS rescore
  5. 2026-06-28 14:06 UTCEPSS rescore
  6. 2026-06-28 04:55 UTCEPSS rescore
  7. 2026-06-28 04:55 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-27 03:07 UTCEPSS rescore
  10. 2026-06-26 11:37 UTCOSV refresh
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 13:48 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:24 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-17 17:52 UTCEPSS rescore
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-16 17:51 UTCEPSS rescore
  27. 2026-06-15 17:47 UTCEPSS rescore
  28. 2026-06-12 23:11 UTCEPSS rescore
  29. 2026-06-12 23:11 UTCEPSS rescore
  30. 2026-06-11 13:59 UTCEPSS rescore
  31. 2026-06-10 22:17 UTCEPSS rescore
  32. 2026-06-10 13:21 UTCEPSS rescore
  33. 2026-06-10 13:21 UTCEPSS rescore
  34. 2026-06-08 18:11 UTCOSV refresh
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-04 13:11 UTCEPSS rescore
  38. 2026-06-04 13:11 UTCEPSS rescore
  39. 2026-06-04 13:11 UTCEPSS rescore
  40. 2026-06-02 20:12 UTCEPSS rescore
  41. 2026-06-02 20:12 UTCEPSS rescore
  42. 2026-05-31 22:30 UTCEPSS rescore
  43. 2026-05-31 22:30 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-27 13:40 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-24 02:12 UTCEG score recompute
  54. 2026-05-24 02:12 UTCVendor advisory

Publicly available exploits

(10 references)

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

  • GitHub PoCNishanthAnand21/CVE-2024-32002-PoC
    First seen Jul 30, 2024

    PoC of CVE-2024-32002 - Remote Code Execution while cloning special-crafted local repositories

    Open source ↗
  • GitHub PoCbfengj/CVE-2024-32002-Exploit
    First seen May 22, 2024
    Open source ↗
  • GitHub PoCYukaFake/CVE-2024-32002-Reverse-Shell
    First seen May 21, 2024

    Este script demuestra cómo explotar la vulnerabilidad CVE-2024-32002 para obtener una reverse shell, proporcionando acceso remoto al sistema afectado. Úselo con precaución en entornos controlados y solo con fines educativos o de pruebas de seguridad.

    Open source ↗
  • GitHub PoCjweny/CVE-2024-32002_HOOK
    First seen May 20, 2024
    Open source ↗
  • GitHub PoCjweny/CVE-2024-32002_EXP
    First seen May 20, 2024
    Open source ↗
  • GitHub PoCsafebuffer/CVE-2024-32002
    First seen May 18, 2024

    CVE-2024-32002 RCE PoC

    Open source ↗
  • GitHub PoCM507/CVE-2024-32002
    First seen May 18, 2024

    local poc for CVE-2024-32002

    Open source ↗
  • GitHub PoCamalmurali47/git_rce
    First seen May 17, 2024

    Exploit PoC for CVE-2024-32002

    Open source ↗
  • GitHub PoCamalmurali47/hook
    First seen May 17, 2024

    Hook for the PoC for exploiting CVE-2024-32002

    Open source ↗
  • GitHub PoCmarkuta/CVE-2024-32002
    First seen May 17, 2024

    A proof of concept for the git vulnerability CVE-2024-32002

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-32002?
CVE-2024-32002 is a critical vulnerability 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, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory.…
When was CVE-2024-32002 disclosed?
CVE-2024-32002 was first published in the National Vulnerability Database on May 14, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32002 actively exploited?
CVE-2024-32002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-32002?
CVE-2024-32002 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2024-32002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-32002, 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-2024-32002

Explore →

Is Your Infrastructure Affected by CVE-2024-32002?

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

Start Free Scan →Browse All CVEs