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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1872 advisory.

    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. (CVE-2026-44471)

    Cargo between 1.68 and 1.96 incorrectly normalized the URLs of third-party registries using the sparse     index protocol. If a hosting provider allowed multiple registries to be hosted with arbitrary names within     the same domain, an attacker able to publish crates in a registry could obtain the credentials of others     users of the same registry. The severity of the vulnerability is **low**, due to the extremely niche     requirements needed to achieve the attack. (CVE-2026-5222)

    A security vulnerability has been detected in libssh2 up to 1.11.1. The impacted element is the function     userauth_password of the file src/userauth.c. Such manipulation of the argument username_len/password_len     leads to integer overflow. The attack may be launched remotely. The name of the patch is     256d04b60d80bf1190e96b0ad1e91b2174d744b1. A patch should be applied to remediate this issue.
    (CVE-2026-7598)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of rust installed on the remote host is prior to 1.96.0-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2-2026-3375 advisory.

    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. (CVE-2026-44471)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2026-1871 advisory.

    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. (CVE-2026-44471)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-44471)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
322058	Amazon Linux 2023 : cargo-c (ALAS2023-2026-1872)	Nessus	Amazon Linux Local Security Checks	medium
322046	Amazon Linux 2 : rust, --advisory ALAS2-2026-3375 (ALAS-2026-3375)	Nessus	Amazon Linux Local Security Checks	high
322022	Amazon Linux 2023 : cargo, clippy, rust (ALAS2023-2026-1871)	Nessus	Amazon Linux Local Security Checks	high
314790	Linux Distros Unpatched Vulnerability : CVE-2026-44471	Nessus	Misc.	high

Detections

Analytics

CVE-2026-44471

high

Tenable Plugins

medium

high

high

high