Skip to main content
VulnerabilityPublished Updated

CVE-2024-35186: Gix index · Traversal outside working tree enables arbitrary code execution

Affects gix-indexSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 0.33.0 soon.

Data as of 9 Nov 2026, 11:22 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.33.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade gix-index to 0.33.0.

Affected software

ProductAffectedFixed in
crates.iogix-indexpkg:cargo/gix-indexOther threatsAffected
  • >=0.0.0-0 <0.33.0
Fixed in
  • 0.33.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in gix-index version 0.33.0 that addresses this vulnerability. Users should upgrade to version 0.33.0 or later to remediate the issue. No additional mitigation steps are required if the patch is applied.

Description

CVE-2024-35186 is a vulnerability in gix-index where the software does not properly verify that file paths during checkout remain within the working tree. This allows specially crafted repositories to create or overwrite files outside the intended directory, including in locations where arbitrary code execution can occur, such as .git hooks. The flaw arises from insufficient path validation, enabling directory traversal via tree or blob names containing '..', '.git', or path separators. A fix is available in version 0.33.0.

References

Community reviews

Loading reviews…