CVE-2024-35186 — gix-worktree-state
HIGHCVE-2024-35186 is a high-severity (CVSS 8.8) CWE-23 vulnerability in gix-worktree-state. A fix is available for gix-worktree-state — see the affected versions and patch details below.
gix traversal outside working tree enables arbitrary code execution
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-35186.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-35186 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.0cargo update -p gix-worktree-state --precise 0.11.0 |
| 🦀crates.io | gitoxide | all versions | 0.36.0cargo update -p gitoxide --precise 0.36.0 |
| 🦀crates.io | gix-fs | all versions | 0.11.0cargo update -p gix-fs --precise 0.11.0 |
| 🦀crates.io | gix-worktree | all versions | 0.34.0cargo update -p gix-worktree --precise 0.34.0 |
| 🦀crates.io | gix | all versions | 0.63.0cargo update -p gix --precise 0.63.0 |
| 🦀crates.io | gitoxide-core | all versions | 0.38.0cargo update -p gitoxide-core --precise 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-35186 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2024-35186 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.