# CVE-2026-78676: GitPython before 3.1.59 Remote Code Execution via Config Injection

> Attackers can inject git directives via crafted config files, leading to arbitrary code execution through hook invocation in GitPython.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-78676, ECHO-4174-0632-ee48, GHSA-284h-m62q-gf8w, MINI-3r6g-gxcp-rx46, MINI-3r6x-qh36-cw9c, MINI-5grh-35gp-fmw2, MINI-69pv-xwxq-2392, PYSEC-2026-3786, ROOT-APP-PYPI-CVE-2026-78676

## What is CVE-2026-78676?

CVE-2026-78676 is a critical code injection vulnerability in gitpython-developers GitPython, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-78676?

3 open source packages ship an affected version, including gitpython and GitPython. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitpython` | PyPI | All versions | 3.1.59 |
| `gitpython` | PyPI | All versions | 3.1.59 |
| `GitPython` | PyPI | All versions | 3.1.59 |

Products: Gitpython Project Gitpython.

## How do I fix CVE-2026-78676?

Upgrade gitpython to 3.1.59 or later.

## Is CVE-2026-78676 being exploited?

There is no known exploitation of CVE-2026-78676 in the wild and no public exploit code.

## Other vulnerabilities in gitpython-developers GitPython

- [CVE-2023-40267](https://insights.sbomify.com/CVE-2023-40267/): GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments (critical 9.8)
- [CVE-2026-67324](https://insights.sbomify.com/CVE-2026-67324/): GitPython 3.1.50 Authentication Bypass via Joined Short Options (critical 9.3)
- [CVE-2026-42215](https://insights.sbomify.com/CVE-2026-42215/): GitPython: Command injection via Git options bypass (high 8.8)
- [CVE-2026-87817](https://insights.sbomify.com/CVE-2026-87817/): GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation (high 8.7)
- [CVE-2026-87819](https://insights.sbomify.com/CVE-2026-87819/): GitPython before 3.1.60 Denial of Service via ReDoS (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78676 and fix it if it is affected.

What it is: CVE-2026-78676 is a critical code injection vulnerability in gitpython-developers GitPython, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78676 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitpython (PyPI): affected all versions; fixed in 3.1.59
- gitpython (PyPI): affected all versions; fixed in 3.1.59
- GitPython (PyPI): affected all versions; fixed in 3.1.59

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78676/ (Markdown: https://insights.sbomify.com/CVE-2026-78676/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78676
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78676
- OSV: https://osv.dev/vulnerability/CVE-2026-78676

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78676/
Summaries are generated and may contain mistakes; the official description above is the record.