# GitPython: Unsafe git option guard bypass via single-character kwarg value token smuggling enables arbitrary command execution

Advisory record · `GHSA-r9mr-m37c-5fr3`

- **Identifiers:** `GHSA-r9mr-m37c-5fr3` · `CVE-2026-73625` · `PYSEC-2026-3953`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html) · [CWE-88](https://cwe.mitre.org/data/definitions/88.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md)
- **Published:** 24 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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

## Affected packages

- `gitpython` (PyPI): affected `<3.1.54`; fixed in `3.1.54`

## Machine-written summary

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

> GitPython versions before 3.1.54 (fixed in 3.1.54) can be made to run arbitrary commands with default settings. The unsafe-option check only inspects kwarg names, so an option token hidden in the value of a single-character kwarg is passed to git as a separate argument, such as --upload-pack. An attacker who can supply options to guarded methods like clone_from, fetch, or ls_remote can achieve command execution on the host. Upgrade to GitPython 3.1.54 or later.

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.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0068, the 52nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r9mr-m37c-5fr3)

## Sources

- [GitHub Advisory Database: GHSA-r9mr-m37c-5fr3](https://github.com/advisories/GHSA-r9mr-m37c-5fr3)
- [OSV: GHSA-r9mr-m37c-5fr3](https://osv.dev/vulnerability/GHSA-r9mr-m37c-5fr3)
- <https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-r9mr-m37c-5fr3>
- <https://github.com/gitpython-developers/GitPython/pull/2180>
- <https://github.com/gitpython-developers/GitPython/commit/e8d0fbf774d1f6baa3b481adfe48bd262e43b453>
- <https://github.com/gitpython-developers/GitPython>
- <https://github.com/gitpython-developers/GitPython/releases/tag/3.1.54>

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-r9mr-m37c-5fr3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r9mr-m37c-5fr3/>. Everything for agents: <https://agentprime.io/llms.txt>.