CVE-2025-48384: 
vulnerability analysis and mitigation

Overview

CVE-2025-48384 is a high-severity vulnerability in Git discovered and disclosed on July 8, 2025. The vulnerability affects Git versions prior to 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. This security issue affects macOS and Linux installations of Git, while Windows installations are not vulnerable (Arctic Wolf).

Technical details

The vulnerability stems from Git's handling of trailing carriage return (CR) characters in config values. When reading a config value, Git strips trailing carriage return and line feed (CRLF) characters, but 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. This behavior becomes particularly dangerous when initializing submodules - if a submodule path contains a trailing CR, the altered path can cause Git to initialize the submodule in an unintended location. The vulnerability has been assigned a CVSS v3.1 base score of 8.0 HIGH with the vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H (GitHub Advisory).

Impact

If exploited, the vulnerability can lead to arbitrary code execution. When combined with a symlink pointing to the submodule hooks directory and an executable post-checkout hook, cloning a repository can result in unintended code execution. The vulnerability poses a notable supply chain risk, particularly for developers who regularly work with third-party code (Arctic Wolf).

Exploitability

While the CVSS rating classifies the attack complexity as high, research indicates the vulnerability is trivially exploitable. Threat actors can create malicious git repositories that execute code unexpectedly upon being cloned. The widespread use of the git clone --recursive command pattern, which appears extensively in public GitHub repositories, provides a credible and realistic pretext for exploitation. Proof-of-concept exploit code is publicly available, further lowering the barrier for exploitation (Arctic Wolf).

Mitigation and workarounds

Users are strongly advised to upgrade to the latest fixed versions: v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, or v2.50.1. For macOS users, it's important to note that upgrading Git via package managers like Homebrew does not replace the system version at /usr/bin/git - it installs alongside it and requires updating PATH to use the new version. As an additional security measure, users should avoid cloning untrusted repositories in sensitive environments and avoid using the --recursive switch in the clone command where possible (Arctic Wolf).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

git: 1:2.39.5-0+deb12u3

Fixed

sid

git: 1:2.50.1-0.1

Fixed

trixie

git: 1:2.47.3-0+deb13u1

Fixed

RHEL / CentOS

Fixed

OpenShift

el8:openshift/ose-rhel-coreos-8-0:412.86.202509030110-0

Fixed

RHEL 8

:appstream:git-0:2.43.7-1.el8_10.src

Fixed

RHEL 9

:appstream:git-0:2.31.1-6.el9_0.1.src

Fixed

RHEL 10

git-0:2.47.3-1.el10_0.src

Fixed

Alpine

Fixed

edge

git: 2.50.1-r0

Fixed

v3.19

git: 2.43.7-r0

Fixed

v3.20

git: 2.45.4-r0

Fixed

v3.21

git: 2.47.3-r0

Fixed

v3.22

git: 2.49.1-r0

Fixed

v3.23

git: 2.50.1-r0

Fixed

Source: This report was generated using AI

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management