GitPython is a python library used to interact with Git repositories. Prior to version 3.1.49, GitConfigParser.set_value() passes values to Python's configparser without validating for newlines. GitPython's own _write() converts embedded newlines into indented continuation lines (e.g. \n becomes \n\t), but Git still accepts an indented [core] stanza as a section header — so the injected core.hooksPath becomes effective configuration. Any Git operation that invokes hooks (commit, merge, checkout) will then execute scripts from the attacker-controlled path. This issue has been patched in version 3.1.49.
CVE-2026-44244
This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 85% 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EPSS
- 14.6%
- KEV
- Not listed
Published
May 7, 2026
Last Modified
May 11, 2026
Advisory Details (2)
Auto-updated May 7, 2026Newline injection in config_writer().set_value() enables RCE via core.hooksPath · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-v87r-6q3f-2j67Release 3.1.49 - Security · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/releases/tag/3.1.49Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | python3-git (3.1.24-1ubuntu0.1~esm3) @ jammy | 2026-06-28 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gitpython | 0.1.7 ... 3.1.9 (101 versions) | 3.1.49 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 6× in last 7d / 49× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 128 total refreshes for this CVE.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 09:09 UTCEG score recompute
- 2026-06-28 09:09 UTCVendor advisory
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 14:19 UTCEG score recompute
- 2026-06-27 14:19 UTCVendor advisory
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 22:13 UTCEG score recompute
- 2026-06-26 22:13 UTCVendor advisory
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 03:35 UTCEG score recompute
- 2026-06-17 03:35 UTCVendor advisory
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 02:40 UTCEG score recompute
- 2026-06-15 02:40 UTCVendor advisory
- 2026-06-14 15:50 UTCEG score recompute
- 2026-06-14 15:50 UTCVendor advisory
- 2026-06-14 03:32 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 21:30 UTCEG score recompute
- 2026-06-12 21:30 UTCVendor advisory
- 2026-06-12 05:15 UTCEG score recompute
- 2026-06-12 05:15 UTCVendor advisory
- 2026-06-11 18:25 UTCEG score recompute
- 2026-06-11 18:25 UTCVendor advisory
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 07:23 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 20:32 UTCEG score recompute
- 2026-06-10 20:32 UTCVendor advisory
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 09:41 UTCEG score recompute
- 2026-06-10 09:41 UTCVendor advisory
- 2026-06-09 22:51 UTCEG score recompute
- 2026-06-09 22:51 UTCVendor advisory
- 2026-06-09 09:36 UTCEG score recompute
- 2026-06-09 09:36 UTCVendor advisory
- 2026-06-08 21:57 UTCEG score recompute
- 2026-06-08 21:57 UTCVendor advisory
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 05:06 UTCEG score recompute
- 2026-06-08 05:06 UTCVendor advisory
- 2026-06-07 18:16 UTCEG score recompute
- 2026-06-07 18:16 UTCVendor advisory
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 07:26 UTCEG score recompute
- 2026-06-07 07:26 UTCVendor advisory
- 2026-06-06 20:36 UTCEG score recompute
- 2026-06-06 20:36 UTCVendor advisory
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 09:46 UTCEG score recompute
- 2026-06-06 09:46 UTCVendor advisory
- 2026-06-05 22:55 UTCEG score recompute
- 2026-06-05 22:55 UTCVendor advisory
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 11:43 UTCEG score recompute
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 00:53 UTCEG score recompute
- 2026-06-05 00:53 UTCVendor advisory
- 2026-06-04 13:26 UTCEG score recompute
- 2026-06-04 13:26 UTCVendor advisory
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 02:36 UTCEG score recompute
- 2026-06-04 02:36 UTCVendor advisory
- 2026-06-03 15:46 UTCEG score recompute
- 2026-06-03 15:46 UTCVendor advisory
- 2026-06-03 04:55 UTCEG score recompute
- 2026-06-03 04:55 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(5)
What is CVE-2026-44244?
When was CVE-2026-44244 disclosed?
Is CVE-2026-44244 actively exploited?
What is the CVSS score of CVE-2026-44244?
How do I remediate CVE-2026-44244?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44244
Is Your Infrastructure Affected by CVE-2026-44244?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.