Bug 2513715 - CVE-2026-67323 GitPython: GitPython: Arbitrary code execution via command injection due to unguarded Git options [epel-all]
Summary: CVE-2026-67323 GitPython: GitPython: Arbitrary code execution via command inj...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: GitPython
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Lubomír Sedlář
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["093c4d4a-f86f-42b6-be78-b...
Depends On:
Blocks: CVE-2026-67323
TreeView+ depends on / blocked
 
Reported: 2026-08-10 23:47 UTC by Anten Skrabec
Modified: 2026-08-16 13:13 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Anten Skrabec 2026-08-10 23:47:32 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.

Comment 1 Ben Beasley 2026-08-16 13:13:55 UTC
This is fixed in 3.1.51, which is already in EPEL9 and EPEL10. EPEL8 is at an old version affected by (at this point) dozens of known security issues, but can’t be straightforwardly updated.


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