Bug 2510032 (CVE-2026-67324) - CVE-2026-67324 gitpython: GitPython: Arbitrary Code Execution via Joined Short Options Bypass
Summary: CVE-2026-67324 gitpython: GitPython: Arbitrary Code Execution via Joined Shor...
Keywords:
Status: NEW
Alias: CVE-2026-67324
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:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-01 13:04 UTC by OSIDB Bzimport
Modified: 2026-08-24 16:27 UTC (History)
42 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:59135 0 None None None 2026-08-24 16:26:10 UTC
Red Hat Product Errata RHSA-2026:59136 0 None None None 2026-08-24 16:27:17 UTC

Description OSIDB Bzimport 2026-08-01 13:04:18 UTC 
GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of --upload-pack=<value>) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clone_from(..., multi_options=..., allow_unsafe_options=False), an attacker can supply -u<helper> to bypass the gate that blocks --upload-pack/-u, causing Git to execute the specified helper command during clone. Fixed in 3.1.51.
Comment 3 errata-xmlrpc 2026-08-24 16:26:07 UTC 
This issue has been addressed in the following products:

  Red Hat Ansible Automation Platform 2.5 for RHEL 9
  Red Hat Ansible Automation Platform 2.5 for RHEL 8

Via RHSA-2026:59135 https://access.redhat.com/errata/RHSA-2026:59135
Comment 4 errata-xmlrpc 2026-08-24 16:27:14 UTC 
This issue has been addressed in the following products:

  Red Hat Ansible Automation Platform 2.6 for RHEL 9
  Red Hat Ansible Automation Platform 2.6 for RHEL 10

Via RHSA-2026:59136 https://access.redhat.com/errata/RHSA-2026:59136
Note You need to log in before you can comment on or make changes to this bug.