CVE-2024-22190: Cruft · Untrusted search path under some conditions on Windows allows arbitrary code execution
Affects cruftSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.8 High : upgrade to 2.15.0_6 soon.
Data as of 26 Oct 2026, 17:44 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.15.0_6
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade cruft to 2.15.0_6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewcruftpkg:brew/cruftOther threats | Affected
| Fixed in
|
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 Cruft version 2.15.0_6 that addresses this vulnerability. Users and applications should upgrade to this fixed version to mitigate the risk. Until patched, avoid setting Git.USE_SHELL = True or passing shell=True to GitPython methods on Windows. There is no straightforward mitigation for the hook script scenario other than applying the patch. No vendor advisory states that no action is required or that the issue is already mitigated without patching.
Description
CVE-2024-22190 is a vulnerability in the Cruft Python package on Windows where GitPython uses an untrusted search path under certain conditions, allowing arbitrary code execution. This occurs when GitPython runs git commands through a shell or uses bash.exe to interpret hooks, potentially executing malicious git.exe or bash.exe files from the current directory of an untrusted repository. The issue stems from an incomplete fix for CVE-2023-40590 and affects versions from 2.9.0 up to but not including 2.15.0_6. A fix is available in version 2.15.0_6. The vulnerability has a high severity with a CVSS score of 7.8.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-2mqj-m65w-jghx (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2024-22190 (opens in a new tab)
- github.com/gitpython-developers/GitPython/pull/1792 (opens in a new tab)
- github.com/gitpython-developers/GitPython/commit/ef3192cc414f2fd9978908454f6fd95243784c7f (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/gitpython/PYSEC-2024-4.yaml (opens in a new tab)