CVE-2026-87817Patch(gitpython_project / gitpython)

LOWCVSS 8.7 · HIGH

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

  • Patch gitpython_project gitpython systems immediately
  • Hunt for exploitation attempts and persistence artifacts

Recommended action window: High priority (within 72h)

NVD description

GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.

2.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-94

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • gitpython

Threat summary

  • Exploit tooling references are present in monitored signal
  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Exploit tool or code specified in 1 signal
  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Affected systems

Products
gitpython

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-09: 1Exploit Tool / Code · 2026-09-09: 1Patch / Workaround · 2026-09-09: 1Technical Details · 2026-09-09: 109-09
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨High - GitPython Git Directory Impersonation Code Execution (CVE-2026-87817) GitPython versions before 3.1.60 fail to properly validate that a repository's git directory is legitimate, trusting tracked metadata files like gitdir, commondir, and HEAD without verification. This lets an attacker craft a repository that impersonates its own git directory. By planting a malicious pre-commit hook inside the tracked hooks directory, the attacker gets it to execute the moment a victim calls index.commit() on the cloned or opened repository - turning a routine commit operation into arbitrary code execution. Any application, CI pipeline, or script that uses GitPython to clone or open repositories from untrusted sources is exposed. 👉Upgrade to GitPython 3.1.60.

    Post summary

    GitPython vulnerability CVE‑2026‑87817 allows attackers to execute arbitrary code via malicious pre‑commit hooks; upgrade to version 3.1.60 to remediate.

    0000061
    304 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appgitpython_projectgitpython-python-

Explore more