Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

GitPython submodule update path traversal can write outside the repository

CVE-2026-100689GHSA-59cr-6r3x-644w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gitpython 3.1.62), 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.

Add to your agent

Affected packages

  • PyPI gitpython

    Affected
    <= 3.1.61
    Fixed in
    3.1.62

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.1 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-100689: 0.40% estimated exploitation activity in the next 30 days; percentile 34.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Affected: GitPython 3.1.61 (latest release) and main — git/objects/submodule/base.py. git diff 3.1.61 origin/main -- git/objects/submodule/ is empty, so both are identical here. --- The gap The fix for GHSA-hmq2-w58f-27jc added Submodule.validatedname() and wired it into update() and five siblings, closing the .gitmodules name → .git/modules/<name traversal. The other attacker-controlled .gitmodules field, path, is read raw: and GitPython's own containment guard is applied in only two of the places that consume it: update() validates only the name and then uses the path-derived absolute location directly: So path = ../../../tmp/escaped in an attacker-authored .gitmodules selects the directory that gets created and, on the clone path, populated from the submodule URL. The same absolute location is what forceremove hands to shutil.rmtree. The asymmetry is the argument: this is not a missing concept — the project wrote torelativepath() precisely for this, and add()/move() use it.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-59cr-6r3x-644w

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-59cr-6r3x-644w

  4. Revision 1 · created ·

    Published from ghsa record GHSA-59cr-6r3x-644w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-100689

Advisory: GitPython submodule update path traversal can write outside the repository
IDs: CVE-2026-100689, GHSA-59cr-6r3x-644w
Record: https://patchnext.com/advisories/ghsa-59cr-6r3x-644w (revision 4, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.62. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gitpython: affected <= 3.1.61; fixed in 3.1.62

## 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-59cr-6r3x-644w (GitHub-reviewed advisory GHSA-59cr-6r3x-644w lists affected ranges: PyPI gitpython >=0 <=3.1.61)
- Verified: https://osv.dev/vulnerability/GHSA-59cr-6r3x-644w (OSV record GHSA-59cr-6r3x-644w lists affected ranges: PyPI gitpython >=0 <3.1.62 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…