rust-gix-fs — security 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.
- Products
- rust-gix-fs
- Affected versions
- 0.12.1-1, 0.16.1-1, 0.16.1-2, 0.21.1-1, 0.22.0-1, 0.22.1-1, 0.24.0-1
- Fixed versions
- 0.16.1-2
- CVEs
- CVE-2026-44471
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 17:50 UTC · Revision 2
Source evidence
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.
osv:DEBIAN-CVE-2026-44471
rust-gix-fs
Fixed versions: Not specified
rust-gix-fs
Fixed versions: 0.16.1-2
Complete source record
{
"id": "af8eac95e65fee189448b213ab4c18a1a967d1069f2a52ce01c9baebc96eb986",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-44471",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-44471",
"summary": "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.",
"evidence": "osv:DEBIAN-CVE-2026-44471",
"products": [
{
"name": {
"value": "rust-gix-fs",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "0.12.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "0.16.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "0.16.1-2",
"evidence": "/affected/0/versions"
},
{
"value": "0.21.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "0.22.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "0.22.1-1",
"evidence": "/affected/0/versions"
},
{
"value": "0.24.0-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "rust-gix-fs",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "0.16.1-2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": [
{
"value": "0.12.1-1",
"evidence": "/affected/1/versions"
},
{
"value": "0.16.1-1",
"evidence": "/affected/1/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2026-44471",
"aliases": [
"DEBIAN-CVE-2026-44471"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "rust-gix-fs",
"purl": "pkg:deb/debian/rust-gix-fs?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"0.12.1-1",
"0.16.1-1",
"0.16.1-2",
"0.21.1-1",
"0.22.0-1",
"0.22.1-1",
"0.24.0-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-44471.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "0.16.1-2"
}
]
}
],
"package": {
"name": "rust-gix-fs",
"purl": "pkg:deb/debian/rust-gix-fs?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"0.12.1-1",
"0.16.1-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-44471.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-27T10:01:40.242808032Z",
"provider": "osv",
"upstream": [
"CVE-2026-44471"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-44471"
]
},
"related_cves": [
{
"value": "CVE-2026-44471",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 461354,
"published_at": "2026-05-13T22:16:46.057+00:00"
}