CVE-2025-48384KEV · OVERDUECWE-436CWE-59

Git Link Following Vulnerability

High · published July 8, 2025

Patch now

Confirmed exploited, and the score agrees

CVSS calls it high at 8.0. It is confirmed in active exploitation. It sits in the 91.2th percentile for exploit probability.

404
days past CISA
deadline
CVSS v3.1
8.0
EPSS
4%
Percentile
91.2
In the wild
Confirmed
What it is

🚨 A sneaky CRLF vulnerability lies in Git's handling of submodule paths! An unassuming carriage return could lead to chaos when executing scripts! ⚡ Think of it like a delivery service misreading an address because of an extra line break in the instructions — your package (submodule) ends up in the wrong place, and the delivery driver (Git) accidentally triggers an unexpected surprise (executable hook). An attacker can exploit this vulnerability to execute unintended scripts in your repository after a submodule checkout, potentially leading to data loss or further system compromise. This could disrupt your development processes and create openings for more serious breaches.

Put simply

Think of it like a delivery service misreading an address because of an extra line break in the instructions — your package (submodule) ends up in the wrong place, and the delivery driver (Git) accidentally triggers an unexpected surprise (executable hook). This vulnerability occurs when Git fails to properly quote trailing CR in config values, causing incorrect submodule paths and possibly executing a malicious script if a symlink exists that points to the altered path.

What to do

An attacker can exploit this vulnerability to execute unintended scripts in your repository after a submodule checkout, potentially leading to data loss or further system compromise. This could disrupt your development processes and create openings for more serious breaches. Update your Git installation to at least version 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, or 2.50.1 to mitigate this issue. Be sure to review any submodule paths in your configurations to avoid this sneaky problem. You've got this! Patch your Git and lock down your submodules like the security hero you are! 🛡️

The record
Technical detail
CVSS v3.1
8.0 · HIGH
Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.04379 · 91.2th percentile
Weaknesses
CWE-436 · Interpretation Conflict; CWE-59 · Improper Link Resolution Before File Access ('Link Following')
Published
2025-07-08T23:15Z
KEV added
2025-08-25 · due 2025-09-15
Affected products (10)
ProductVersionsFixed in
git-scm/git< 2.43.72.43.7
git-scm/git≥ 2.44.0, < 2.44.42.44.4
git-scm/git≥ 2.45.0, < 2.45.42.45.4
git-scm/git≥ 2.46.0, < 2.46.42.46.4
git-scm/git≥ 2.47.0, < 2.47.32.47.3
git-scm/git≥ 2.48.0, < 2.48.22.48.2
git-scm/git≥ 2.49.0, < 2.49.12.49.1
git-scm/git≥ 2.50.0, < 2.50.12.50.1
debian/debian_linuxall versions—
apple/xcode< 26.026.0
References (5)
EPSS history
Timeline
  • 25 AUG 00:00Z
    Added to CISA KEV — remediate by Sep 15
    kev
  • 08 JUL 18:23Z
    Git allows arbitrary code execution through broken config quoting
    cvelistv5