cve.bz

CVE-2026-78676 gitpython project gitpython: Argument Injection

9.3 criticalExploit referenceEPSS 0.6%Fix available

Critical (9.3) in gitpython project gitpython. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in gitpython 3.1.59.

On this page
GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-08-26. 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-88 Improper Neutralization of Argument Delimiters in a Command (Argument Injection)
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-78676 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78676?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78676?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-78676 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.59

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-284h-m62q-gf8wPyPIgitpython<3.1.593.1.59
PYSEC-2026-3786PyPIgitpython<3.1.593.1.59

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12python-git3.1.30-1+deb12u3DEBIAN-CVE-2026-78676
Debian13python-git3.1.44-1+deb13u1DEBIAN-CVE-2026-78676
Debian14python-git3.1.61-1DEBIAN-CVE-2026-78676
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
openSUSETumbleweedpython-GitPython3.1.59-3.1openSUSE-SU-2026:11615-1
Alpinev3.24py3-gitpython3.1.61-r0ALPINE-CVE-2026-78676

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

Case for AC:H (8.1): the trigger needs two things the attacker does not

straightforwardly own:

(1) a crafted multi-line quoted value must already sit DORMANT in .git/config

— the guarded set_value() path will not put it there; it must arrive via

_read() of a file the attacker influenced but does not directly write; and

(2) a SUBSEQUENT, UNRELATED GitPython config WRITE must fire to re-serialize

and corrupt it — and that write is performed by the victim application on

its own schedule, not by the attacker.

"Prepare the target environment" + "conditions beyond the attacker's control"

is the textbook AC:H definition; step (2) in particular fits it.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream GitPython project has fixed this issue in version 3.1.59; updating GitPython to this or a later version is the available remediation.

ProductPackageStateAdvisory
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:1791253059Fixed 2026-10-08RHSA-2026:79378
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/hub-rhel9:1791254555Fixed 2026-10-08RHSA-2026:79378
Red Hat OpenShift AI 2.25rhoai/odh-feature-server-rhel9:1792148523Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1791869442Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9:1791870787Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-minimal-cuda-py312-rhel9:1791867222Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-minimal-rocm-py312-rhel9:1791903144Fixed 2026-10-21RHSA-2026:87410
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9:1791867191Fixed 2026-10-21RHSA-2026:87410
Exploit Intelligenceexploit-intelligence-tech-preview/vulnerability-analysis-rhel9Will not fix
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Affected
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Not affected
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-rhel8Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Not affected
Red Hat Ansible Automation Platform 2automation-controllerNot affected
77 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-78676.

Attack patterns (CAPEC)

  • CAPEC-41 Using Meta-characters in E-mail Headers to Inject Malicious Payloads Likelihood: High · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-137 Parameter Injection Likelihood: Medium · Severity: Medium
  • CAPEC-174 Flash Parameter Injection Likelihood: High · Severity: Medium
  • CAPEC-460 HTTP Parameter Pollution (HPP) Severity: Medium

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

References

Check your stackJSON