Skip to main content
EPSS 0.3%top 76%

CVE-2026-67326: Improper Input Validation in gitpython-developers GitPython

0
High
Published: 08/01/2026 (08/01/2026, 12:22:18 UTC)
Source: CVE Database V5
Vendor/Project: gitpython-developers
Product: GitPython

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 v4.0

Score 7.3high

Attack Vector
Local
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
Passive
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

gitpython-developers

GitPython

Affected versions
>=0 <3.1.50
gitpython
pkg:pypi/gitpython
Affected versions
<3.1.50

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/16/2026, 13:42:33 UTC

Technical Analysis

CVE-2026-67326 is an input validation vulnerability in GitPython prior to version 3.1.50. The config_writer() function does not properly validate newline characters in its section parameter, allowing attackers to inject arbitrary section headers into the .git/config file. This can be exploited to create a malicious [core] section with hooksPath configured to attacker-controlled locations, leading to remote code execution upon execution of git hooks.

Potential Impact

Successful exploitation allows an attacker with local access to inject arbitrary configuration sections into the .git/config file. This can lead to remote code execution when git hooks are triggered, posing a high security risk.

Mitigation Recommendations

No official patch or remediation level is currently confirmed. Users should upgrade to GitPython version 3.1.50 or later once available. Until then, restrict access to GitPython environments and avoid processing untrusted input in config_writer(). Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-07-29T13:07:21.184Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a6deb26bf32cb7a34c1fc19

Added to database: 08/01/2026, 12:48:38 UTC

Last enriched: 08/16/2026, 13:42:33 UTC

Last updated: 09/10/2026, 19:56:12 UTC

Views: 46

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses