External Control of File Name or Path Affecting git-for-windows/git package, versions [,2.55.0.windows.4)
Threat Intelligence
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-GITFORWINDOWSGIT-19233835
- published24 Aug 2026
- disclosed22 Aug 2026
- credit0xmrma
Introduced: 22 Aug 2026
NewCVE-2026-62960 (opens in a new tab)How to fix?
Upgrade git-for-windows/git to version 2.55.0.windows.4 or higher.
Overview
Affected versions of this package are vulnerable to External Control of File Name or Path via the fetch_bundle_list() and copy_uri_to_file() path in bundle-uri.c. An attacker can trigger a Windows client to contact an attacker-chosen UNC host and expose NTLM credentials by advertising a bundle-uri such as //attacker/share/poc.bundle or file:////attacker/share/poc.bundle on a remote repository and having the victim clone with transfer.bundleuri=true. The vulnerable code accepts server-advertised bundle URIs that are not HTTP(S) and treats them as local file paths, so git clone follows the remote-provided path instead of rejecting it. On Windows, that turns a clone of an untrusted remote into an outbound SMB open against the attacker-controlled host, with the resulting credential exposure and network callback impacting the user.