# CVE-2026-44471: gitoxide: Symlink prefix-reuse allows worktree escape during checkout

> A malicious git tree allows attackers to write symlinks to arbitrary directories during checkout, bypassing path validation checks in gitoxide.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** DEBIAN-CVE-2026-44471, GHSA-f89h-2fjh-2r9q, MINI-rc87-q9jv-5mh8, UBUNTU-CVE-2026-44471

## What is CVE-2026-44471?

CVE-2026-44471 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

gitoxide is an implementation of git written in Rust. Prior to 0.21.1, a malicious tree can be constructed that will, when checked out with gitoxide, permit writing an attacker-controlled symlink into any existing directory the user has write access to. During checkout, all symlink index entries are deferred and created after regular files using a single shared gix_worktree::Stack. Internally, this uses a gix_fs::Stack. gix_fs::Stack::make_relative_path_current() caches validated path prefixes: when the previously-processed leaf component exactly matches the leading component(s) of the next path, the leaf-to-directory transition at gix-fs/src/stack.rs invokes only delegate.push_directory(), never delegate.push(). In gix_worktree::stack::delegate::StackDelegate, when the state member is State::CreateDirectoryAndAttributesStack, Attributes::push_directory() only loads attributes (from the ODB, in the clone case), and does not perform any other checks. The on-disk symlink_metadata() check and unlink-on-collision live in StackDelegate::push()'s invocation of create_leading_directory(), which is therefore bypassed for the cached prefix. The final symlink is created with plain std::os::unix::fs::symlink, which follows symlinks in parent directories. Therefore, it's possible to provide a tree with duplicate symlink and directory entries that exploits this. This vulnerability is fixed in 0.21.1.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-44471?

2 open source packages ship an affected version, including gix-fs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gix-fs` | crates.io | All versions | 0.21.1 |
| `gix-fs` | crates.io | All versions | 0.21.1 |

Products: Gitoxidelabs Gix-Fs.

## How do I fix CVE-2026-44471?

Upgrade gix-fs to 0.21.1 or later.

## Is CVE-2026-44471 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44471 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44471 and fix it if it is affected.

What it is: CVE-2026-44471 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44471 exists.

Affected packages and fixed versions:
- gix-fs (crates.io): affected all versions; fixed in 0.21.1
- gix-fs (crates.io): affected all versions; fixed in 0.21.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44471/ (Markdown: https://insights.sbomify.com/CVE-2026-44471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44471
- OSV: https://osv.dev/vulnerability/CVE-2026-44471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44471/
Summaries are generated and may contain mistakes; the official description above is the record.