cve.bz

CVE-2026-67323 gitpython project gitpython

8.6 highExploit referenceEPSS 1.3%Fix available

High (8.6) in gitpython project gitpython. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in gitpython 3.1.51.

On this page
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

CVSS 4.0

8.6 high
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

CVSS 3.1

8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 70th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-77 Improper Neutralization of Special Elements used in a Command
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67323 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67323?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67323?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67323 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gitpython-developers GitPythonbefore 3.1.51

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-956x-8gvw-wg5vPyPIgitpython<3.1.513.1.51
PYSEC-2026-3839PyPIgitpython<3.1.513.1.51

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12python-git3.1.30-1+deb12u3DEBIAN-CVE-2026-67323
Debian13python-git3.1.44-1+deb13u1DEBIAN-CVE-2026-67323
Debian14python-git3.1.61-1DEBIAN-CVE-2026-67323
Ubuntu26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 morepython-gitno fix listedUBUNTU-CVE-2026-67323
Red Hatansible_automation_platform:2.5::el8automation-controller-cli, automation-controller-venv-tower0:4.6.32-1.el8apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el8automation-gateway-server0:2.5.20260824-1.el8apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el8python3.12-aiohttp0:3.14.3-1.el8apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el8python3.12-gitpython0:3.1.59-1.el8apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el8, ansible_automation_platform_developer:2.5::el8python3.12-django0:5.2.17-1.el8apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el9automation-controller-cli, automation-controller-venv-tower0:4.6.32-1.el9apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el9automation-gateway-server0:2.5.20260824-1.el9apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el9python3.12-aiohttp0:3.14.3-1.el9apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el9python3.12-gitpython0:3.1.59-1.el9apRHSA-2026:59135
Red Hatansible_automation_platform:2.5::el9, ansible_automation_platform_developer:2.5::el9python3.12-django0:5.2.17-1.el9apRHSA-2026:59135
Red Hatansible_automation_platform:2.6::el9automation-controller-cli, automation-controller-venv-tower0:4.7.16-1.el9apRHSA-2026:59136
Red Hatansible_automation_platform:2.6::el9automation-platform-ui0:2.6.13-1.el9apRHSA-2026:59136
10 more for Red Hat in the JSON and on Red Hat's page.
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morepython-GitPython3.1.34.1693646983.2a2ae77-150400.9.8.1SUSE-SU-2026:4072-1
openSUSELeap 16.0python-GitPython3.1.44-160000.4.1openSUSE-SU-2026:21874-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is an Important vulnerability because it allows for arbitrary code execution or file truncation. The flaw in GitPython requires an application to process attacker-controlled input through specific GitPython methods, such as Repo.archive() or git.ls_remote(), to be exploited. This could lead to a compromise of confidentiality, integrity, and availability on affected Red Hat products that utilize GitPython in such a manner.

Red Hat's mitigation

To mitigate the risk, ensure that applications utilizing GitPython are run within a sandboxed environment with minimal privileges. This limits the potential impact of arbitrary command execution or file truncation if an attacker successfully exploits the vulnerability through an application processing untrusted input. Review applications that interact with GitPython to ensure all input is properly sanitized and validated before being passed to methods such as Repo.archive(), git.ls_remote(), Repo.iter_commits(), or Repo.blame().

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8python3.12-gitpython-0:3.1.59-1.el8apFixed 2026-08-24RHSA-2026:59135
Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller-0:4.6.33-1.el8apFixed 2026-09-23RHSA-2026:71114
Red Hat Ansible Automation Platform 2.5 for RHEL 9python3.12-gitpython-0:3.1.59-1.el9apFixed 2026-08-24RHSA-2026:59135
Red Hat Ansible Automation Platform 2.5 for RHEL 9automation-controller-0:4.6.33-1.el9apFixed 2026-09-23RHSA-2026:71114
Red Hat Ansible Automation Platform 2.6 for RHEL 9python3.12-gitpython-0:3.1.59-1.el9apFixed 2026-08-24RHSA-2026:59136
Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller-0:4.7.17-1.el9apFixed 2026-09-23RHSA-2026:71113
Red Hat Ansible Automation Platform 2.5ansible-automation-platform-25/controller-rhel8:1789607021Fixed 2026-09-23RHSA-2026:71210
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/controller-rhel9:1789673739Fixed 2026-09-23RHSA-2026:71179
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/controller-rhel9:1788918363Fixed 2026-09-14RHSA-2026:67279
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/hub-rhel9:1788918708Fixed 2026-09-14RHSA-2026:67279
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Affected
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Affected
Pen Drive Powered by Red Hat Lightspeedpen-drive/pen-drive-scanner-rhel9Affected
Red Hat AI Inference Serverrhaiis/vllm-cpu-rhel9Will not fix
Red Hat AI Inference Serverrhaiis/vllm-tpu-rhel9Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/controller-rhel8Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/hub-rhel8Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/hub-rhel8Will not fix
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Will not fix
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Affected
58 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67323.

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-40 Manipulating Writeable Terminal Devices Likelihood: High · Severity: Very High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-136 LDAP Injection Likelihood: High · Severity: High
  • CAPEC-183 IMAP/SMTP Command Injection Severity: Medium
  • CAPEC-248 Command Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON