CVE-2026-76221

GitPython before 3.1.58 contains a config-name injection flaw (CWE-74) in its option-name validator, allowing equals signs, hash symbols, and whitespace to be smuggled into git-config option names. When an attacker can influence an option name, an injected string such as 'sshCommand = touch /tmp/RCE #' forges additional git-config directives beyond the intended one. On the next git operation, the forged core.sshCommand or core.hooksPath directives cause attacker-controlled commands to execute on the host running GitPython, yielding code execution with the privileges of that process. Any application, automation, or tooling embedding vulnerable GitPython versions where low-privileged attackers can shape git-config option names is affected. Exploitation has not been observed at scale: there is one public proof-of-concept advisory (GHSA-jm78-9fvv-mhgr), EPSS is 0.5% (40th percentile), and the flaw is not in CISA's KEV catalog.

What to do: Upgrade GitPython to 3.1.58 or later, which fixes the option-name validator. Audit code paths where git-config option names come from untrusted sources (repository data, remotes, or user input) and restrict what option names are passed to GitPython until patched.