CVE-2024-52005

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd 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 week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

January 15, 2025

Last Modified

December 18, 2025

Advisory Details (2)

Auto-updated Aug 24, 2026
Patch available. Sources: github.
Web page

[ANNOUNCE] Git for Windows 2.47.1(2) (security release) - Johannes Schindelin

https://lore.kernel.org/git/[email protected]
GitHub advisoryMentions a patch (unverified)

The sideband payload is passed unfiltered to the terminal · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-7jjc-gg6m-3329

Vendor Advisories for CVE-2024-52005(7)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgit-0:2.43.5-3.el8_102025-06-03redhat
redhatdiscovery/discovery-server-rhel9:1.14.3-17485292792025-06-02redhat
redhatgit-0:2.39.5-1.el9_2.12025-05-15redhat
redhatgit-0:2.43.5-1.el9_4.12025-05-15redhat
redhatgit-0:2.47.1-2.el9_62025-05-13redhat
redhatgit-0:2.47.1-2.el10_02025-05-13redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.30.2-1 ... 1:2.55.0-1 (99 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.39.2+next.20230215-1 ... 1:2.55.0-1 (46 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.47.2-0.2 ... 1:2.55.0-1 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.47.2-0.2 ... 1:2.55.0-1 (17 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 36× 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 93 of 191 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2024-52005?
CVE-2024-52005 is a high-severity vulnerability; its CVE record was published on January 15, 2025. Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the…
When was the CVE record for CVE-2024-52005 published?
The CVE record for CVE-2024-52005 was published on January 15, 2025. 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 December 18, 2025; the record at its source may have been updated since.
Is CVE-2024-52005 actively exploited?
CVE-2024-52005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52005?
CVE-2024-52005 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-52005?
A fix for CVE-2024-52005 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-52005 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-52005

Explore →

Is Your Infrastructure Affected by CVE-2024-52005?

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

Book a Demo →Browse All CVEs