CVE-2025-48385: Git alllows arbitrary file writes via bundle-uri parameter injection
CVE-2025-48385 is regarding a vulnerability in Git where when cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. GitHub created this CVE on their behalf. The documented Visual Studio updates incorporate updates in Git which address this vulnerability. Please see CVE-2025-48385 for more information.
Other sources
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 cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. 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
GitHub: CVE-2025-48385 Git Protocol Injection Vulnerability
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.43.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.44.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.45.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.46.4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.47.3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.48.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.49.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v2.50.1 - Configuration
To avoid bundle-uri protocol injection paths, disable/adjust the bundle behavior controlled by the bundle.heuristic config option (bundle URIs are not enabled by default).
Git bundle.heuristic = disable bundle-uri / bundle behavior that can be controlled by the bundle
Event History
Frequently Asked Questions
What is the severity of CVE-2025-48385?
CVE-2025-48385 has been assigned a high severity rating due to its potential impact on repository integrity and security.
How do I fix CVE-2025-48385?
To fix CVE-2025-48385, update to the latest versions of Visual Studio 2019 or 2022 as specified in the official remedies from Microsoft.
Which versions of software are affected by CVE-2025-48385?
CVE-2025-48385 affects Visual Studio 2019 version 16.11 and Visual Studio 2022 versions 17.8, 17.12, and 17.14.
What product does CVE-2025-48385 pertain to?
CVE-2025-48385 pertains to vulnerabilities found in Git when integrated with Microsoft Visual Studio.
Is there public disclosure information available for CVE-2025-48385?
Yes, there is public disclosure information available for CVE-2025-48385 through Microsoft's update guide and GitHub security advisories.