Code execution via unescaped config section names
Published Aug 3, 2026 · Updated Aug 3, 2026
Config injection in GitPython before 3.1.53 allows attackers to execute code through a malicious submodule name. _assure_config_name_safe rejects only CR, LF, and NUL, so bracket, quote, and comment syntax becomes a second section in .git/config. Execution requires an application to create the named submodule or update submodules from an untrusted repository before Git invokes an injected core.sshCommand during an SSH operation.
Summary
What happened
Config injection in GitPython before 3.1.53 allows attackers to execute code through a malicious submodule name. _assure_config_name_safe rejects only CR, LF, and NUL, so bracket, quote, and comment syntax becomes a second section in .git/config. Execution requires an application to create the named submodule or update submodules from an untrusted repository before Git invokes an injected core.sshCommand during an SSH operation.
The record
- CVE
- CVE-2026-69097
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- GitPython Developers
- Product
- GitPython
- Classifications
- CWE-74, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.53
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.
Weakness, pattern, technique
Public exploit references
- Upstream inert-marker configuration-injection proof of conceptproof 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