CVE-2026-67323

Description

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.

Severity
HIGH
CVSS v3
8.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H · source cna
CVSS v4
8.6
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · source cna
Exploit chance (EPSS)
1.251%
chance of exploitation in the next 30 days
higher than 69.9% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 2
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impacttotal
Scored2026-08-04

Timeline

  1. 2026-07-21GitHub advisory published (GHSA-956x-8gvw-wg5v)11 days before publication
  2. 2026-08-01Published by the CNA12:22 UTC
  3. 2026-08-04CISA SSVC decision recorded3 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-956x-8gvw-wg5v, affected packages:

PackageVulnerable versionsFixed in
PyPI gitpythonbefore 3.1.513.1.51

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
gitpython_project gitpythonbefore 3.1.51fixed in 3.1.513.1.51

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources