Git Link Following Vulnerability
git — git
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.
8.1
2.8%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
- Published
- Jul 8, 2025
- Modified
- Feb 26, 2026
- Added to KEV
- Aug 25, 2025
- Federal patch due
- Sep 15, 2025
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2025-48384, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2025-48384 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2025-48384?
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.
How severe is CVE-2025-48384?
CVE-2025-48384 has a CVSS base score of 8.1 out of 10 (CVSS 3.1).
Is CVE-2025-48384 actively exploited in the wild?
Yes. CVE-2025-48384 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Aug 25, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-48384?
2.8% - meaning FIRST.org's EPSS model estimates a 2.8% probability this vulnerability will be exploited in the wild within 30 days (85% percentile among all scored CVEs).
What type of vulnerability is CVE-2025-48384?
CVE-2025-48384 is classified under CWE-436, CWE-59 (CWE-436: Interpretation Conflict).
Cross-checked against
Impactr finds and proves whether CVE-2025-48384 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist