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.
CVE-2024-35186
HIGHNVD 8.88.8—Elevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 41% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 52.8%
- KEV
- Not listed
Published
May 23, 2024
Last Modified
April 15, 2026
Advisory Details (1)
Auto-updated May 22, 2026🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available
Traversal outside working tree enables arbitrary code execution · Advisory · GitoxideLabs/gitoxide · GitHub
https://github.com/Byron/gitoxide/security/advisories/GHSA-7w47-3wg8-547cAffected Packages
(7 across 1 ecosystem)
crates.io(7)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gitoxide | — | 0.36.0 | — |
| gitoxide-core | — | 0.38.0 | — |
| gix | — | 0.63.0 | — |
| gix-fs | — | 0.11.0 | — |
| gix-index | — | 0.33.0 | — |
| gix-worktree | — | 0.34.0 | — |
| gix-worktree-state | — | 0.11.0 | — |
Frequently asked(5)
What is CVE-2024-35186?
CVE-2024-35186 is a high vulnerability published on May 23, 2024. 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…
When was CVE-2024-35186 disclosed?
CVE-2024-35186 was first published in the National Vulnerability Database on May 23, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-35186 actively exploited?
CVE-2024-35186 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-35186?
CVE-2024-35186 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-35186?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-35186, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-35186
Is Your Infrastructure Affected by CVE-2024-35186?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.