gix and gitoxide's symlinked .gitmodules are followed and parsed from outside of the repository
Affects gitoxideSource GCVE Database
Public exploit available · CVSS 8.7 High : upgrade to 0.52.1 as a priority.
Data as of 27 Oct 2026, 01:47 UTC
- Patch
- Available – fixed in 0.52.1, 0.83.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:PWhat to do
Upgrade gitoxide to 0.52.1; gix to 0.83.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crates.iogitoxide | Affected
| Fixed in
|
| crates.iogix | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in gitoxide versions 0.52.1 and 0.83.0 that addresses this issue. The recommended fix is to avoid silently following symlinks when loading the worktree .gitmodules file. Possible mitigations include rejecting symlinked .gitmodules files, verifying that the canonicalized target remains inside the repository worktree before reading, or loading .gitmodules from the index or HEAD tree for security-sensitive use cases. Users should upgrade to the fixed versions to remediate this vulnerability.
Description
gitoxide versions prior to 0.52.1 and 0.83.0 have a vulnerability where the .gitmodules file in the worktree can be a symlink pointing outside the repository. This causes the submodule metadata API to parse and expose attacker-controlled data from outside the repository boundary. The flaw allows injection of arbitrary submodule configuration metadata, misleading downstream workflows that rely on this data. No direct code execution is claimed, but the integrity of submodule metadata is compromised.