# CVE-2026-100419: gitoxide gix-fs before 0.23.0 Worktree Escape via Symlink

> Attackers can escape worktree directories via symlink manipulation during forced checkout, enabling arbitrary file writes and potential code execution.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 25 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** AZL-105332, AZL-105335, DEBIAN-CVE-2026-100419, GHSA-jjhr-hr59-47h4, UBUNTU-CVE-2026-100419

## What is CVE-2026-100419?

CVE-2026-100419 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 25 Sep 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 gix-fs before 0.23.0 contains a path validation bypass vulnerability in the worktree checkout mechanism that allows attackers to escape the worktree directory via symlink manipulation. During forced checkout with overwrite_existing enabled, attackers can craft malicious repository trees where symlink entries replace validated directories, causing subsequent files to be written outside the worktree through the symlink for code execution or file manipulation.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-100419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100419 is a high-severity path traversal vulnerability in GitoxideLabs gitoxide, published on 25 Sep 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-100419 exists.

Affected product: GitoxideLabs gitoxide. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-100419/ (Markdown: https://insights.sbomify.com/CVE-2026-100419/index.md)
```

## Sources

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

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