CVE-2025-48385

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 1.1% (64th 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.6EG
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: 1.1%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 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
1.1%
EPSS %ILE
64th
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.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 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
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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

July 8, 2025

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated Sep 1, 2026
Patch available. Sources: github.
Web page

oss-security - Multiple vulnerabilities fixed in Git

http://www.openwall.com/lists/oss-security/2025/07/08/4
GitHub advisoryMentions a patch (unverified)

Arbitrary file writes via bundle-uri parameter injection · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-m98c-vgpc-9655

Vendor Advisories for CVE-2025-48385(17)

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

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugitweb (1:2.34.1-1ubuntu1.13) @ jammy2026-06-08ubuntu
redhatopenshift/ose-rhel-coreos-9:413.92.202509030117-02025-09-18redhat
redhatdevspaces/code-rhel9:3.23-17576188072025-09-15redhat
redhatweb-terminal/web-terminal-tooling-rhel9:1.11-82025-09-15redhat
redhatweb-terminal/web-terminal-tooling-rhel9:1.12-42025-09-15redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202508261955-02025-09-04redhat
redhatopenshift/ose-rhel-coreos-9:414.92.202508270040-02025-09-04redhat
redhatopenshift/ose-rhel-coreos-9:417.94.202508141510-02025-08-27redhat
redhatopenshift/ose-rhel-coreos-9:415.92.202508192014-02025-08-27redhat
redhatopenshift/ose-rhel-coreos-9:4.19.9.6.202508112354-02025-08-20redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202508060022-02025-08-13redhat
redhatrhpam-7/rhpam-smartrouter-rhel8:7.13.5-4.17526769302025-08-07redhat
redhatgit-0:2.39.5-1.el9_2.22025-07-28redhat
redhatgit-0:2.39.5-1.el8_8.22025-07-28redhat
redhatgit-0:2.43.5-1.el9_4.22025-07-24redhat
redhatgit-0:2.43.7-1.el8_102025-07-23redhat
redhatgit-0:2.47.3-1.el10_02025-07-22redhat
redhatgit-0:2.47.3-1.el9_62025-07-21redhat

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

(9 across 9 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.43.7-r0: fixed in 2.43.7-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.45.4-r0: fixed in 2.45.4-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.47.3-r0: fixed in 2.47.3-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.49.1-r0: fixed in 2.49.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.50.1-r0: fixed in 2.50.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 2.50.1-r0: fixed in 2.50.1-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.39.2+next.20230215-1, 1:2.39.2-1.1, 1:2.39.5-0+deb12u1, 1:2.39.5-0+deb12u2
  • every version up to 1:2.39.5-0+deb12u3: fixed in 1:2.39.5-0+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.47.2-0.2
  • every version up to 1:2.47.3-0+deb13u1: fixed in 1:2.47.3-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.47.2-0.2 ... 1:2.50.0~rc0+next.20250528-1 (9 versions)
  • every version up to 1:2.50.1-0.1: fixed in 1:2.50.1-0.1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 9× in last 7d / 35× 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 221 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 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2025-48385?
CVE-2025-48385 is a high-severity vulnerability; its CVE record was published on July 8, 2025. Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to…
When was the CVE record for CVE-2025-48385 published?
The CVE record for CVE-2025-48385 was published on July 8, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-48385 actively exploited?
CVE-2025-48385 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-48385?
CVE-2025-48385 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-48385?
A fix for CVE-2025-48385 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-48385 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-2025-48385

Explore →

Is Your Infrastructure Affected by CVE-2025-48385?

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

Book a Demo →Browse All CVEs