CVE-2024-35186
HIGHCVE-2024-35186 is a high-severity (CVSS 8.8) CWE-23 vulnerability in gix-worktree-state. O3 Security confirms whether CVE-2024-35186 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
gix traversal outside working tree enables arbitrary code execution
Blast Radius
gix-worktree-state🦀gitoxide🦀gix-fs🦀gix-worktree🦀gix🦀gitoxide-core🦀gix-indexReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
gitoxide is a pure Rust implementation of Git. During checkout, gix-worktree-state 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. This vulnerability leads to a major loss of confidentiality, integrity, and availability, but creating files outside a working tree without attempting to execute code can directly impact integrity as well. This vulnerability has been patched in version(s) 0.36.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | gix-worktree-state | all versions | 0.11.0 |
| 🦀crates.io | gitoxide | all versions | 0.36.0 |
| 🦀crates.io | gix-fs | all versions | 0.11.0 |
| 🦀crates.io | gix-worktree | all versions | 0.34.0 |
| 🦀crates.io | gix | all versions | 0.63.0 |
| 🦀crates.io | gitoxide-core | all versions | 0.38.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gix-worktree-state. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update gix-worktree-state to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-35186 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-35186 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-35186. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-35186 in your dependencies?
O3 detects CVE-2024-35186 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.