GitPython: Unguarded git option forwarding in IndexFile.checkout() and TagReference.create() enables arbitrary file overwrite and arbitrary file read
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (gitpython 3.1.57), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI gitpython
- Affected
- <= 3.1.56
- Fixed in
- 3.1.57
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3f7w-8rr8-f37f lists affected ranges: PyPI gitpython >=0 <=3.1.56
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Target: gitpython-developers/GitPython Tested: HEAD 07e80555 (2026-07-25), latest release 3.1.55, git version 2.50.1 Reported instances: 2 exploitable, from a sweep of 14 unguarded call sites Summary GitPython blocks dangerous git options through Git.checkunsafeoptions(), gated per method by an allowunsafeoptions parameter. That guard is applied per call site, so any API that forwards kwargs into a git command without calling it passes caller-controlled options straight to git. A mechanical sweep of every method that forwards kwargs into a .git.<command(...) call found 14 sites with no guard. Two reach a git option that takes a filesystem path: |
| Call site | git option | Impact | |---|---|---|---| | 1 | IndexFile.checkout() → git checkout-index | --prefix=<path | arbitrary file overwrite with repository-controlled content | | 2 | TagReference.create() → git tag | -F <file / --file=<file | arbitrary file read, returned in-band | This is the same defect class already fixed in…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-3f7w-8rr8-f37f
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-3f7w-8rr8-f37f Advisory: GitPython: Unguarded git option forwarding in IndexFile.checkout() and TagReference.create() enables arbitrary file overwrite and arbitrary file read IDs: GHSA-3f7w-8rr8-f37f Record: https://patchnext.com/advisories/ghsa-3f7w-8rr8-f37f (revision 1, source checked 26 Oct 2026, 13:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: gitpython 3.1.57. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI gitpython: affected <= 3.1.56; fixed in 3.1.57 ## Suggested inspection (read-only) - `python -m pip show gitpython`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on gitpython. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-3f7w-8rr8-f37f (GitHub-reviewed advisory GHSA-3f7w-8rr8-f37f lists affected ranges: PyPI gitpython >=0 <=3.1.56) Commands are suggestions: review each one before running it.
Loading voting…