Interpretation Conflict Affecting git/git package, versions [,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)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-GITGIT-10664667
- published9 Jul 2025
- disclosed8 Jul 2025
- creditDavid Leadbeater
Introduced: 8 Jul 2025
NewCVE-2025-48384 (opens in a new tab)How to fix?
Upgrade git/git to version 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, 2.50.1 or higher.
Overview
Affected versions of this package are vulnerable to Interpretation Conflict in the process of reading and writing configuration values, where improper handling of trailing carriage return characters can alter submodule paths. An attacker can execute arbitrary code by crafting a submodule path with a trailing carriage return and leveraging a symlink to redirect the altered path to a hooks directory containing a malicious executable script.
Note:
This is only exploitable if a symlink exists from the altered submodule path to the submodule hooks directory and the submodule contains an executable post-checkout hook.
Workaround
For users that are unable to upgrade to the fixed version it is recommended to avoid recursively cloning submodules in untrusted repositories.