Code execution via newline-injected Git configuration
Published Aug 1, 2026 · Updated Aug 1, 2026
Improper input validation in GitPython before 3.1.50 allows attackers to execute code by injecting section headers into .git/config. GitConfigParser.set_value() passes the section argument to configparser without rejecting newlines, and its writer serializes the injected text as a second valid section header. Exploitation requires attacker control of a section name and a later hook-triggering Git operation; a forged core.hooksPath then runs code from an attacker-controlled directory.
Summary
What happened
Improper input validation in GitPython before 3.1.50 allows attackers to execute code by injecting section headers into .git/config. GitConfigParser.set_value() passes the section argument to configparser without rejecting newlines, and its writer serializes the injected text as a second valid section header. Exploitation requires attacker control of a section name and a later hook-triggering Git operation; a forged core.hooksPath then runs code from an attacker-controlled directory.
The record
- CVE
- CVE-2026-67326
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- GitPython Developers
- Product
- GitPython
- Classifications
- CWE-20, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.50
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitPython config_writer section-injection PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo