CVE-2025-48384
HIGHCISA KEVEPSS 85th pctlDescription
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 to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 85% of all known CVEs.
Git Link Following Vulnerability
Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Remediation due: 2025-09-15
References
Related Vulnerabilities
Other CWE-59 (Link Following) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-30333 | High | 7.5 | 99% | KEV + Ransom | Fix |
| CVE-2021-21300 | High | 8.0 | 89% | - | Fix |
| CVE-2021-32610 | High | 7.1 | 73% | - | Fix |
| CVE-2020-36193 | High | 7.5 | 71% | KEV | Fix |
| CVE-2023-40028 | Medium | 4.9 | 58% | - | Fix |
| CVE-2023-36874 | High | 7.8 | 43% | KEV | Fix |
Common questions
How do I fix CVE-2025-48384?
Published advisories record a fix for 76 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2025-48384 being actively exploited?
Yes. CVE-2025-48384 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2025-09-15. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2025-48384?
CVE-2025-48384 has a CVSS v3 base score of 8.0, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2025-48384 affect?
Published advisories record a fix for git (Debian), emacs-git (Rocky), emacs-git (Red Hat / RHEL), emacs-git-el (Red Hat / RHEL), and 72 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2025-48384
Markdown
[](https://tridentstack.com/cve/CVE-2025-48384)HTML
<a href="https://tridentstack.com/cve/CVE-2025-48384"><img src="https://tridentstack.com/cve/badge/CVE-2025-48384.svg" alt="CVE-2025-48384"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-11-06.