CVE-2026-44244: GitPython · Newline injection in config_writer().set_value() enables RCE via core.hooksPath
Affects nbdimeSource GCVE Database
Not known to be exploited · CVSS 7.8 High : upgrade to 4.0.4_2 soon.
Data as of 26 Oct 2026, 17:27 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 4.0.4_2
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 nbdime to 4.0.4_2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewnbdimepkg:brew/nbdimeOther 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 4.0.4_2 that rejects values containing carriage return (CR), line feed (LF), or NUL characters in config_writer().set_value(). Users should upgrade to this fixed version to prevent injection of malicious configuration values. The recommended remediation approach is to raise an error when such characters are detected rather than silently stripping them, to avoid masking unsanitized input issues. Audit any usage of config_writer().set_value() in applications that accept external input to ensure proper sanitization or upgrading to the fixed version.
Description
GitPython's config_writer().set_value() method does not validate input values for newline characters, allowing injection of a malicious core.hooksPath configuration. This enables an attacker to control Git hook execution paths, potentially leading to remote code execution during Git operations that invoke hooks. The vulnerability affects GitPython versions from 1.1.0 up to but not including 4.0.4_2. A fix is available in version 4.0.4_2 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)