CVE-2025-48384

CRITICALNVD 8.09.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-08-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.0 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 4%CVSS: 8.0Exploit: cisa kev · ssvc active · public exploitExposed: 0

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 reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. 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.0
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
4%
EPSS %ILE
90%
KEV
⚠ Exploited

Published

July 8, 2025

Last Modified

November 6, 2025

Advisory Details (5)

Auto-updated Jun 3, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
generic Patch Available

[SECURITY] [DLA 4323-1] git security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
generic

oss-security - Multiple vulnerabilities fixed in Git

http://www.openwall.com/lists/oss-security/2025/07/08/4
generic

Full Disclosure: APPLE-SA-09-15-2025-12 Xcode 26

http://seclists.org/fulldisclosure/2025/Sep/60
github Patch Available

Arbitrary code execution through broken config quoting · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9

Vendor Advisories for CVE-2025-48384(20)

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.7.4-0ubuntu1.10+esm9) @ xenial2026-09-05ubuntu
redhatrhcos-413.92.202509030117-02025-09-18redhat
redhatweb-terminal/web-terminal-tooling-rhel9:1.12-42025-09-15redhat
redhatweb-terminal/web-terminal-tooling-rhel9:1.11-82025-09-15redhat
redhatrhcos-412.86.202509030110-02025-09-11redhat
redhatrhcos-416.94.202508261955-02025-09-04redhat
redhatrhcos-414.92.202508270040-02025-09-04redhat
redhatrhcos-417.94.202508141510-02025-08-27redhat
redhatrhcos-415.92.202508192014-02025-08-27redhat
redhatrhcos-4.19.9.6.202508112354-02025-08-20redhat
redhatrhcos-418.94.202508060022-02025-08-13redhat
redhatrhpam-7/rhpam-smartrouter-rhel8:7.13.5-4.17526769302025-08-07redhat
redhatgit-0:2.31.1-6.el9_0.12025-07-28redhat
redhatgit-0:2.27.0-5.el8_4.12025-07-28redhat
redhatgit-0:2.31.8-3.el8_6.12025-07-28redhat
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.18.4-5.el8_2.12025-07-24redhat
redhatgit-0:1.8.3.1-25.el7_9.12025-07-24redhat
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

(10 across 10 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
git—2.43.7-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
git—2.45.4-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
git—2.47.3-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
git—2.49.1-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
git—2.50.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
git—2.50.1-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
git1:2.30.2-1, 1:2.30.2-1+deb11u1, 1:2.30.2-1+deb11u2, 1:2.30.2-1+deb11u3, 1:2.30.2-1+deb11u41:2.30.2-1+deb11u5—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
git1:2.39.2+next.20230215-1, 1:2.39.2-1.1, 1:2.39.5-0+deb12u1, 1:2.39.5-0+deb12u21:2.39.5-0+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
git1:2.47.2-0.21:2.47.3-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
git1:2.47.2-0.2 ... 1:2.50.0~rc0+next.20250528-1 (9 versions)1:2.50.1-0.1—

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

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 61× in last 7d / 262× 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.

Showing the most recent 100 of 830 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

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

  • GitHub PoCliamg/CVE-2025-48384
    First seen Jul 9, 2025

    PoC for CVE-2025-48384

    Open source ↗
  • GitHub PoCacheong08/CVE-2025-48384
    First seen Jul 8, 2025

    Breaking git with a carriage return and cloning RCE

    Open source ↗

Frequently asked(6)

What is CVE-2025-48384?
CVE-2025-48384 is a critical vulnerability 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 reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with…
When was CVE-2025-48384 disclosed?
CVE-2025-48384 was first published in the National Vulnerability Database on July 8, 2025, with the most recent update on November 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-48384 actively exploited?
Yes. CISA added CVE-2025-48384 to the Known Exploited Vulnerabilities catalog on August 25, 2025, affecting Git Git. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-48384?
CVE-2025-48384 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.
Which products are affected by CVE-2025-48384?
CVE-2025-48384 affects Git Git. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-48384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-48384, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-48384

Explore →

Is Your Infrastructure Affected by CVE-2025-48384?

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

Start Free Scan →Browse All CVEs