Skip to content
Fencer Intel
high 7.0

CVE-2026-67326 json

GitPython before 3.1.50 Newline Injection via config_writer section

published 6mo ago modified 19d ago also EUVD-2026-51814 , GHSA-mv93-w799-cj2w , PYSEC-2026-3980

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section headers into .git/config. Attackers can inject newlines to create a forged [core] section with hooksPath pointing to attacker-controlled directories, achieving remote code execution when git hooks are triggered.

Patch / fix

  • pypi gitpython 3.1.50
  • gitpython-developers GitPython 3.1.50
  • python-git Debian 12 3.1.30-1+deb12u3
  • python-git Debian 13 3.1.44-1+deb13u1
  • python-git Debian 14 3.1.50-1

debian advisories DEBIAN-CVE-2026-67326

  • lld21 hummingbird 1 21.1.8-8.hum1
  • lldb21 hummingbird 1 21.1.8-8.hum1
  • llvm21 hummingbird 1 21.1.8-8.hum1
  • clang21 hummingbird 1 21.1.8-8.hum1
  • libomp21 hummingbird 1 21.1.8-8.hum1
  • lld21-libs hummingbird 1 21.1.8-8.hum1
  • llvm21-libs hummingbird 1 21.1.8-8.hum1
  • llvm21-test hummingbird 1 21.1.8-8.hum1

red hat advisories RHSA-2026:45940RHSA-2026:44416RHSA-2026:45785

  • python-GitPython SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +8 more 3.1.34.1693646983.2a2ae77-150400.9.8.1

suse advisories SUSE-SU-2026:4072-1

  • python-GitPython openSUSE Leap 16.0 3.1.44-160000.4.1
  • python-GitPython openSUSE Tumbleweed 3.1.58-1.1

opensuse advisories openSUSE-SU-2026:21874-1openSUSE-SU-2026:11466-1

Is CVE-2026-67326 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67326 updated cvss 7.0

gitpython: GitPython: Remote Code Execution via Newline Injection in config_writer()

  • Red Hat Hardened Images lld 22.1.8-4.1.hum1, lld21 21.1.8-8.hum1, lldb 22.1.8-4.1.hum1, lldb21 21.1.8-8.hum1, llvm 22.1.8-4.1.hum1, llvm21 21.1.8-8.hum1, +39 more
    fixed: vendor fix RHSA-2026:44416
  • Red Hat Hardened Images rust 1.97.1-2.hum1
    not affected: component not present
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
3mo ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-mv93-w799-cj2w referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 7.3 CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 4.0 7.3 CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi gitpython
<3.1.50
3.1.50

Affected products

  • gitpython-developers GitPython

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of gitpython-developers/GitPython published their own advisory on GitHub. Reviewed sources take precedence over it.