CVE-2025-48384
CVE-2025-48384 is a high-severity vulnerability (CVSS 3.1 score 8.1). Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files. CISA added it to the Known Exploited Vulnerabilities catalog on 2025-08-25, with a remediation due date of 2025-09-15 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 4.5% probability of exploitation in the next 30 days, in the 91st percentile of scored CVEs.
Updated
Git Link Following Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
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.
CISA notes
This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. For more information, please see: https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9 ; https://access.redhat.com/errata/RHSA-2025:13933 ; https://alas.aws.amazon.com/AL2/ALAS2-2025-2941.html ; https://linux.oracle.com/errata/ELSA-2025-11534.html ; https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-48384 ; https://nvd.nist.gov/vuln/detail/CVE-2025-48384
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2025-48384 to the KEV catalog 48 days after its CVE record was published. The median for entries added in 2025 is 26 days.
- Its current EPSS score (4.5%) is higher than that of 15% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:HThe source's number matches none of this vector's scores. Its Base score is 8.0.
Open in CVSS calculatorRemediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-08-26).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| git | git git | < 2.43.7 >= 2.44.0-rc0, < 2.44.4 >= 2.45.0-rc0, < 2.45.4 >= 2.46.0-rc0, < 2.46.4 >= 2.47.0-rc0, < 2.47.3 >= 2.48.0-rc0, < 2.48.2 >= 2.49.0-rc0, < 2.49.1 >= 2.50.0-rc0, < 2.50.1 |
References
4 linksRecord Details
- Published
- 2025-07-08
- Last updated
- 2026-02-26
- Assigner (CNA)
- GitHub_M
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.