Cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3agitpython_projectgitpythonpython/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 25 Aug 2026 04:05:22 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgRemote Code Execution in GitPython via Git Config Injectionhttps://feed.craftedsignal.io/briefs/2026-08-gitpython-rce/Tue, 25 Aug 2026 04:05:22 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-gitpython-rce/GitPython versions before 3.1.59 contain a vulnerability where improper sanitization of multi-line configuration values allows attackers to inject arbitrary git directives, leading to remote code execution.GitPython is a Python library used to interact with Git repositories. A critical vulnerability (CVE-2026-78676) exists in versions prior to 3.1.59 due to improper re-serialization of multi-line configuration values during git-config write operations. An attacker can supply a specially crafted configuration value containing embedded newlines. When GitPython performs a write operation on the configuration file, these newlines cause the injected content to be interpreted as new, live git configuration directives. A primary vector involves the injection of a malicious core.hooksPath, which directs Git to execute arbitrary code from a location controlled by the attacker whenever a Git hook is triggered. This vulnerability enables unauthenticated remote code execution in environments where GitPython processes untrusted configuration data.

Attack Chain

  1. The attacker provides a malicious, multi-line string intended to be written to a .git/config file (e.g., through an application interface using GitPython).
  2. The application uses the vulnerable GitPython library to update the repository configuration with the attacker-controlled input.
  3. GitPython fails to escape or neutralize the newline characters within the input string during the serialization process.
  4. The serialized output is written to the .git/config file, effectively terminating the intended configuration key and starting a new directive on the subsequent line.
  5. The injected directive, such as core.hooksPath = /tmp/malicious_hooks_dir, is successfully written into the configuration file.
  6. The system or user triggers a standard Git operation (e.g., git commit or git push) within the repository.
  7. Git reads the corrupted configuration file and executes the malicious scripts located in the attacker-specified hooks directory.
  8. Final objective achieved: Remote code execution under the context of the user running the Git operation.

Impact

The vulnerability carries a CVSS score of 9.8, indicating a critical risk of complete system compromise. Successful exploitation allows for unauthenticated remote code execution, which can lead to data exfiltration, unauthorized access to internal development environments, and the deployment of persistent backdoors within software supply chains. Any system or automated pipeline utilizing GitPython to manage repository configurations with untrusted input is at risk.

Recommendation

  • Upgrade the GitPython library to version 3.1.59 or later immediately to address CVE-2026-78676.
  • Audit application code that passes user-supplied input to GitPython's configuration write functions.
  • Implement strict input validation to ensure configuration values do not contain newline characters or unexpected git directives.
  • Review logs for unauthorized modifications to .git/config files within critical infrastructure or CI/CD environments.
]]>highadvisoryvulnerabilitypath-traversalgitpythonsupply-chaininfo-disclosurelocal-file-inclusion