CVE-2026-44244: GitPython · Newline injection in config_writer().set_value() enables RCE via core.hooksPath
Affects cruftSource GCVE Database
Not known to be exploited · CVSS 7.8 High : upgrade to 2.16.0_8 soon.
Data as of 26 Oct 2026, 17:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.16.0_8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 May 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.16.0_8.
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 fix is available in GitPython version 2.16.0_8 that rejects values containing carriage return, line feed, or NUL characters in set_value(). Users should upgrade to this version or later. The recommended remediation is to raise an error on such characters rather than silently stripping them, to avoid masking unsanitized input. Applications using config_writer().set_value() with external input should audit and sanitize inputs to prevent injection. No other mitigations are specified.
Description
GitPython's config_writer().set_value() method does not validate newline characters in values, allowing injection of new configuration sections such as core.hooksPath. This enables attackers to control Git hook execution paths, leading to remote code execution when Git operations invoke hooks. The vulnerability affects GitPython versions from 2.9.0 up to but not including 2.16.0_8. A fix is available in version 2.16.0_8 that rejects values containing CR, LF, or NUL characters.
References
- github.com/gitpython-developers/GitPython/security/advisories/GHSA-v87r-6q3f-2j67 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-44244 (opens in a new tab)
- github.com/gitpython-developers/GitPython (opens in a new tab)
- github.com/gitpython-developers/GitPython/releases/tag/3.1.49 (opens in a new tab)