CVE-2025-48384: Git Link Following Vulnerability
CVE-2025-48384 is regarding a vulnerability in Git where 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. GitHub created this CVE on their behalf. The documented Visual Studio updates incorporate updates in Git which address this vulnerability. Please see CVE-2025-48384 for more information.
Other sources
Dev Tools. A path handling issue was addressed with improved validation.
— Apple
Dev Tools. The issue was addressed with improved checks.
— Apple
Git contains a link following vulnerability that stems from Git’s inconsistent handling of carriage return characters in configuration files.
— CISA
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.
— NVD
Git. This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.
— Apple
Credit
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-48384?
CVE-2025-48384 is rated as a critical vulnerability due to its potential impact on the security of configurations in affected software.
How do I fix CVE-2025-48384?
To fix CVE-2025-48384, update your Visual Studio installation to the latest version provided by Microsoft.
Which versions of Visual Studio are affected by CVE-2025-48384?
CVE-2025-48384 affects Visual Studio 2017 versions 15.0 - 15.9, Visual Studio 2019 version 16.11, and various versions of Visual Studio 2022.
What types of attacks could exploit CVE-2025-48384?
Exploitation of CVE-2025-48384 could allow an attacker to manipulate configuration settings leading to unauthorized access or denial of service.
Is there a workaround for CVE-2025-48384 if I cannot update immediately?
Currently, applying available patches from Microsoft is the recommended action, as no known effective workarounds exist for CVE-2025-48384.