gix traversal outside working tree enables arbitrary code execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-35186: 0.82% estimated exploitation activity in the next 30 days; percentile 57.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary During checkout, gitoxide does not verify that paths point to locations in the working tree. A specially crafted repository can, when cloned, place new files anywhere writable by the application. Details Although gix-worktree-state checks for collisions with existing files, it does not itself check if a path is really in the working tree when performing a checkout, nor do the path checks in gix-fs and gix-worktree prevent this. Cloning an untrusted repository containing specially crafted tree or blob names will create new files outside the repository, or inside the repository or a submodule's .git directory. The simplest cases are: - A tree named .. to traverse upward. This facilitates arbitrary code execution because files can be placed in one or more locations where they are likely to be executed soon. - A tree named .git to enter a .git directory. This facilitates arbitrary code execution because hooks can be installed. A number of alternatives that achieve the same effect…

Published by the source

22 May 2024, 14:05 UTC

Last modified by the source

7 Aug 2024, 05:01 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7w47-3wg8-547c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-35186

Advisory: gix traversal outside working tree enables arbitrary code execution
IDs: CVE-2024-35186, GHSA-7w47-3wg8-547c
Record: https://patchnext.com/advisories/cve-2024-35186 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix 0.63.0; gix-index 0.33.0; gitoxide 0.36.0; gix-fs 0.11.0; gitoxide-core 0.38.0; gix-worktree 0.34.0; gix-worktree-state 0.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix: affected < 0.63.0; fixed in 0.63.0
- crates.io gix-index: affected < 0.33.0; fixed in 0.33.0
- crates.io gitoxide: affected < 0.36.0; fixed in 0.36.0
- crates.io gix-fs: affected < 0.11.0; fixed in 0.11.0
- crates.io gitoxide-core: affected < 0.38.0; fixed in 0.38.0
- crates.io gix-worktree: affected < 0.34.0; fixed in 0.34.0
- crates.io gix-worktree-state: affected < 0.11.0; fixed in 0.11.0

## Suggested inspection (read-only)
- crates.io gix: check the installed version with your package manager.
- crates.io gix-index: check the installed version with your package manager.
- crates.io gitoxide: check the installed version with your package manager.
- crates.io gix-fs: check the installed version with your package manager.
- crates.io gitoxide-core: check the installed version with your package manager.
- crates.io gix-worktree: check the installed version with your package manager.
- crates.io gix-worktree-state: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix, gix-index, gitoxide, gix-fs, gitoxide-core, gix-worktree, gix-worktree-state.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7w47-3wg8-547c (GitHub-reviewed advisory GHSA-7w47-3wg8-547c lists affected ranges: crates.io gix-worktree-state >=0 =0 =0 =0 =0 =0 =0 <0.33.0)

Commands are suggestions: review each one before running it.