Bug 2467804 (CVE-2026-44244) - CVE-2026-44244 GitPython: GitPython: Arbitrary code execution via injected newlines in Git configuration
Summary: CVE-2026-44244 GitPython: GitPython: Arbitrary code execution via injected ne...
Keywords:
Status: NEW
Alias: CVE-2026-44244
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2516147 2517355 2517356
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-07 19:01 UTC by OSIDB Bzimport
Modified: 2026-08-17 11:01 UTC (History)
55 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-07 19:01:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.