The vulnerability arises from improper link resolution before file access in gitoxide versions before 0.21.1. During checkout, symlink entries are deferred and created after regular files using shared internal stacks that cache validated path prefixes. This caching causes a bypass of critical checks such as on-disk symlink metadata verification and unlink-on-collision, allowing creation of attacker-controlled symlinks in arbitrary writable directories. The final symlink creation uses standard Unix symlink calls that follow symlinks in parent directories, enabling exploitation via crafted trees with duplicate symlink and directory entries. The issue is tracked as CWE-59 and fixed in gitoxide 0.21.1.

Successful exploitation allows an attacker to write symbolic links controlled by the attacker into any directory where the user has write access during a git checkout operation. This can lead to unauthorized file system modifications, potentially compromising confidentiality, integrity, and availability of data. The CVSS v3.1 score is 7.8 (high), reflecting local attack vector with low complexity, no privileges required, user interaction needed, and high impact on confidentiality, integrity, and availability.

A fix for this vulnerability is included in gitoxide version 0.21.1. Users should upgrade to version 0.21.1 or later to remediate this issue. Patch status is not explicitly confirmed beyond this version update; therefore, users should consult the official GitoxideLabs advisories or repositories for the latest remediation details. Until patched, avoid checking out untrusted repositories with vulnerable gitoxide versions.