CVE-2026-44471

rust-gix-fs: gitoxide is an implementation of git written in Rust

CVE-2026-44471 is fixed in 25 products on 1 platform, first by DEBIAN-CVE-2026-44471, released May 27, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.8
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0029
21st percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
cargo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
cargo-c · amzn 2023 0.10.19-1.amzn2023.0.3 ALAS2023-2026-1872 Jun 22, 2026
cargo-c-debuginfo · amzn 2023 0.10.19-1.amzn2023.0.3 ALAS2023-2026-1872 Jun 22, 2026
cargo-debuginfo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
clippy · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
clippy-debuginfo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-analyzer · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-analyzer-debuginfo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-cargo-c-debugsource · amzn 2023 0.10.19-1.amzn2023.0.3 ALAS2023-2026-1872 Jun 22, 2026
rust-debugger-common · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-debuginfo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-debugsource · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-doc · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-gdb · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-gix-fs · Debian 14 0.16.1-2 DEBIAN-CVE-2026-44471 May 27, 2026
rust-lldb · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-src · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-std-static · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-std-static-wasm32-unknown-unknown · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-std-static-wasm32-wasip1 · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-toolset · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rust-toolset-srpm-macros · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rustfmt · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026
rustfmt-debuginfo · amzn 2023 1.96.0-1.amzn2023.0.2 ALAS2023-2026-1871 Jun 22, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.