Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker operates malicious Git server
-
DeliveryServer advertises UNC or file-scheme bundle URI
-
ExploitVictim initiates git clone or fetch with transfer.bundleuri=true
-
ExecutionGit passes URI to Windows as a filesystem path
-
PersistWindows initiates outbound SMB connection to attacker host
-
ImpactAttacker captures NTLM authentication material
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the victim has explicitly set transfer.bundleuri=true in their Git configuration-this setting is disabled by default and must be manually enabled by the user or an administrator. The victim must perform a git clone or git fetch from an attacker-controlled or attacker-compromised remote Git server capable of advertising custom bundle URIs. The vulnerability is limited to Git for Windows; Linux and macOS Git clients are not affected. Exploitation is additionally constrained by the requirement for user interaction (the clone or fetch must be actively initiated) and by network egress policies: environments that block outbound SMB traffic on ports 445 and 139 to external hosts prevent NTLM exposure at the network layer even if the vulnerable code path executes. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N scores 7.4 High and accurately characterizes the threat: network-reachable, low attack complexity, no attacker privileges required, with a scope change because captured NTLM credentials can authenticate against Active Directory, file servers, and other Windows services far beyond the Git process itself. EPSS data was not supplied in the source intelligence, so exploitation probability cannot be quantified numerically. The absence of a CISA KEV listing and the lack of public exploit code reduce urgency relative to a fully weaponized issue. The primary mitigating factor is that transfer.bundleuri=true is non-default and must be explicitly enabled; organizations that have not set this option are entirely unexposed. The conceptual simplicity of the attack-operate a Git server, advertise a malicious URI, wait for a clone-means any team enabling bundleuri against untrusted or community-hosted remotes faces meaningful risk, particularly given how straightforwardly NTLM relay can escalate into lateral movement on Windows networks. |
| Exploit ScenarioDerived | An attacker hosts a public or compromised Git repository and configures it to advertise a bundle URI pointing to an attacker-controlled SMB share (e.g., \\attacker-host\share\bundle.bundle). A developer running Git for Windows with transfer.bundleuri=true clones or fetches from that repository, causing Windows to automatically initiate an SMB connection and present NTLM credentials to the attacker's host. The attacker captures the NTLM hash for offline cracking or relays it in real time to authenticate against the victim organization's internal Windows services. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 21, 2026
NTLM credential exposure in Git for Windows before 2.55.0.windows.4 allows a malicious remote Git server to capture Windows authentication material by advertising a crafted bundle URI during clone or fetch operations. When transfer.bundleuri is enabled, non-HTTP(S) URIs including bare UNC paths are treated as local filesystem paths, causing Windows to initiate an outbound SMB connection to an attacker-controlled host and expose NTLM hashes. No public exploit code has been identified at time of analysis and no CISA KEV listing is present, but the technique maps directly onto well-documented NTLM capture and relay attack patterns.
RemediationAI
Upgrade to Git for Windows version 2.55.0.windows.4 or later, available at https://github.com/git-for-windows/git/releases/tag/v2.55.0.windows.4. If immediate upgrade is not feasible, ensure transfer.bundleuri is not set to true in any Git configuration scope (user, system, or repository level); the default is disabled, so this requires no affirmative action on unmodified installations and eliminates the attack surface entirely with no impact on standard clone and fetch workflows. As a network-level compensating control, enforcing egress firewall rules that block outbound SMB on ports 445 and 139 to external hosts will prevent NTLM credential exposure even if the vulnerable code path is triggered-however, this does not fix the underlying flaw and may break legitimate SMB-dependent workflows in some environments. Full advisory details are at https://github.com/git-for-windows/git/security/advisories/GHSA-xrpg-8j9v-v282.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in bundle-uri.c within Git for Windows (CPE: cpe:2.3:a:git-for-windows:git:*:*:*:*:*:*:*:*), specifically traversing transport_get_remote_bundle_uri(), fetch_bundle_uri_internal(), and copy_uri_to_file(). The Bundle URI feature, enabled via transfer.bundleuri=true, lets Git servers advertise pre-packaged bundle files to accelerate clone and fetch. The root cause is CWE-200 (Exposure of Sensitive Information): advertised URIs were not validated against Git's transport protocol allowlist before processing. Non-HTTP(S) values-bare UNC paths like \\attacker\share\bundle and file:// URIs after prefix stripping-were forwarded to Windows as filesystem paths, which the OS resolved via SMB, triggering automatic NTLM authentication to the attacker-controlled host. The fix in commit a93524749d7806870fd2b4b00a3812da1d6e5f4a adds sanitize_bundle_list(), which determines each advertised URI's protocol (defaulting to 'file' for bare or UNC paths) and rejects any scheme not permitted by protocol.*.allow-which denies 'file' by default.
Know when Git gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
Network vector; no attacker privileges needed; user interaction required for the clone or fetch; scope change because captured NTLM credentials enable authentication against systems beyond the Git client.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Git for Windows is the Windows port of Git. Prior to 2.55.0.windows.4, a malicious remote Git server can advertise a bundle URI that reaches transport_get_remote_bundle_uri(), fetch_bundle_uri_internal(), and copy_uri_to_file() in bundle-uri.c during clone or fetch when transfer.bundleuri=true. Non-HTTP(S) values are treated as local filesystem paths, and file URI prefixes are removed, so a bare UNC path or file URI targeting an attacker-controlled share causes Windows to initiate an outbound SMB connection. This can expose NTLM authentication material to the attacker-selected host. This issue is fixed in version 2.55.0.windows.4.
Executive ViewAI
Git for Windows versions before 2.55.0.windows.4 expose Windows NTLM authentication credentials to malicious Git servers through a bundle URI handling vulnerability. Organizations using affected Git for Windows versions are at risk of credential theft when developers interact with untrusted or compromised Git repositories. Captured credentials could enable unauthorized access to internal systems and lateral movement within the enterprise.
Apply vendor patch: Update Git for Windows to 2.55.0.windows.4 or later. Interim mitigation if patch unavailable: Disable transfer.bundleuri configuration; restrict outbound SMB connections from developer workstations via firewall or endpoint controls.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL ca
git-shell in git before 2.4.12, 2.5.x before 2.5.6, 2.6.x before 2.6.7, 2.7.x before 2.7.5, 2.8.x before 2.8.5, 2.9.x be
Git contains a CRLF injection vulnerability (CVE-2025-48384, CVSS 8.0) in its config handling that allows attackers to e
Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x be
The (1) git-remote-ext and (2) unspecified other remote helper programs in Git before 2.3.10, 2.4.x before 2.4.10, 2.5.x
Git is an open-source distributed revision control system. Rated high severity (CVSS 7.5), this vulnerability is remotel
Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) ma
The package git before 1.11.0 are vulnerable to Command Injection via git argument injection. Rated critical severity (C
revision.c in git before 2.7.4 uses an incorrect integer data type, which allows remote attackers to execute arbitrary c
contrib/completion/git-prompt.sh in Git before 1.9.3 does not sanitize branch names in the PS1 variable, allowing a mali
Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote
EUVD-2026-64126
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB