gix-fs before 0.24.1 NTLM Credential Disclosure via Windows Symlink UNC Probe
- Exploited
- No known exploitation
- Fix
- Fixed in 0.24.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Windows with symbolic link support enabled Victim runs Windows with symbolic link creation enabled (Developer Mode or administrator) Victim has network connectivity to the attacker's SMB endpoint Victim clones or checks out the attacker's crafted repository Affected gix-fs versions before 0.24.1
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.58% · 48th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
gix-fs in gitoxide before 0.24.1 contains a credential disclosure vulnerability that allows remote attackers to capture NTLM credentials by supplying UNC symlink targets in a crafted repository. When a victim checks out the repository on Windows with symlinks enabled, gix_fs::symlink::create calls is_dir() on the UNC target, triggering SMB authentication that leaks the username, domain, and NTLMv2 hash.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Windows with symbolic link support enabled Victim runs Windows with symbolic link creation enabled (Developer Mode or administrator) Victim has network connectivity to the attacker's SMB endpoint Victim clones or checks out the attacker's crafted repository Affected gix-fs versions before 0.24.1Upgrade to a fixed version: 0.24.1.
Workaround: Check out untrusted repositories only with symlink support disabled
Timeline
- CVE published
- First seen by cve.now
Affected versions
- GitoxideLabs gitoxide
fixed in 0.24.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123532
Is CVE-2026-123532 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When gitoxide checks out a repository on Windows with symbolic link support enabled, a crafted symlink can make the machine connect to an attacker's SMB endpoint. That connection can leak the Windows username, domain, and NTLMv2 response hash to the attacker.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-123532?
gitoxide: before 0.24.1.Source: cve.now feed data
Am I affected, and how do I check?
gix-fs in gitoxide before 0.24.1 is affected, and only on Windows with symbolic link creation enabled (Developer Mode or administrator), when the machine can reach an attacker's SMB endpoint during a clone or checkout. To check, look at the gitoxide version in your project's Cargo.lock or installed gix binary, and check whether Developer Mode is on or the account has administrator rights.Source: github.com, vulncheck.com
How do I fix CVE-2026-123532?
Upgrade gitoxide and gix-fs to 0.24.1 or later. Until then, check out untrusted repositories only with symbolic link support disabled.Source: github.com, vulncheck.com