# GitPython has Command Injection via Git options bypass

Advisory record · `GHSA-rpm5-65cw-6hj4`

- **Identifiers:** `GHSA-rpm5-65cw-6hj4` · `CVE-2026-42215` · `PYSEC-2026-2160`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md)
- **Published:** 25 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Apr 2026, 23:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gitpython` (PyPI): affected `>=3.1.30, <3.1.47`; fixed in `3.1.47`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GitPython versions from 3.1.30 before 3.1.47 are affected. The unsafe-option guard blocks options such as upload-pack and receive-pack but not their underscore spellings (upload_pack and receive_pack) passed as Python keyword arguments to clone_from, fetch, pull, or push. If an application passes attacker-controlled keyword arguments into these calls, an attacker can run arbitrary commands as the application's account, even with allow_unsafe_options left at its default. Upgrade to GitPython 3.1.47 or later; no other workaround is listed.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0075, the 55th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 7 May 2026, 19:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-42215)
- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rpm5-65cw-6hj4)

## Sources

- [GitHub Advisory Database: GHSA-rpm5-65cw-6hj4](https://github.com/advisories/GHSA-rpm5-65cw-6hj4)
- [OSV: GHSA-rpm5-65cw-6hj4](https://osv.dev/vulnerability/GHSA-rpm5-65cw-6hj4)
- <https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-rpm5-65cw-6hj4>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-42215>
- <https://github.com/gitpython-developers/GitPython>
- <https://github.com/gitpython-developers/GitPython/releases/tag/3.1.47>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-rpm5-65cw-6hj4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rpm5-65cw-6hj4/>. Everything for agents: <https://agentprime.io/llms.txt>.
