Secuno
ENNL
Book demo

CVE-2026-67326

7.0 HIGHPublic exploitEPSS 0.32%
  1. Published1 Aug 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityHigh
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Gitpython Project Gitpython< 3.1.50

Remediation

Fixed in
Gitpython Project Gitpython≥ 3.1.50

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-202379.1
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-880648.8
Backstage is an open framework for building developer portals. Prior to 1.14.6 and from…
CVE-2026-917389.6
Improper input validation in ANGLE in Google Chrome prior to 153.0.8010.47 allowed a…
CVE-2026-794108.1
Improper validation of the quantity parameter in the add-to-cart path of Webkul Bagisto…
CVE-2026-586918.4
In FsmReleaseKey of fsm.c, there is a possible permission bypass due to improper input…
CVE-2026-586838.8
In IP Multimedia Subsystem, there is a possible out-of-bounds write due to improper…

Frequently asked

Is CVE-2026-67326 being actively exploited?

CVE-2026-67326 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.32%.

How severe is CVE-2026-67326?

CVE-2026-67326 has a CVSS 3.1 base score of 7.0, rated high. EPSS estimates a 0.32% probability of exploitation.

Which products are affected by CVE-2026-67326?

Affected products include Gitpython Project Gitpython.

How do I fix CVE-2026-67326?

Upgrade affected software to a fixed version, for example Gitpython Project Gitpython 3.1.50 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-67326 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.