CVE-2026-87817

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-3.1.60-remote-code-execution-via-git-directory-impersonation
github Patch Available🟡 PoC Available

Repository content can impersonate the git directory, leading to arbitrary code execution · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-239g-whfq-7xj9

Vendor Advisories for CVE-2026-87817(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (112 versions)3.1.60

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 01:32 UTCEG score recompute
  2. 2026-09-19 01:32 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 13:59 UTCGHSA enrichment
  5. 2026-09-18 02:25 UTCEG score recompute
  6. 2026-09-18 02:25 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 14:51 UTCGHSA enrichment
  9. 2026-09-17 03:17 UTCGHSA enrichment
  10. 2026-09-16 15:43 UTCEG score recompute
  11. 2026-09-16 15:43 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 10:12 UTCEG score recompute
  14. 2026-09-16 10:12 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 22:37 UTCGHSA enrichment
  17. 2026-09-15 11:03 UTCEG score recompute
  18. 2026-09-15 11:03 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 23:29 UTCGHSA enrichment
  21. 2026-09-14 11:54 UTCGHSA enrichment
  22. 2026-09-14 00:20 UTCEG score recompute
  23. 2026-09-14 00:20 UTCGHSA enrichment
  24. 2026-09-13 12:46 UTCGHSA enrichment
  25. 2026-09-13 01:12 UTCEG score recompute
Show 19 more
  1. 2026-09-13 01:12 UTCGHSA enrichment
  2. 2026-09-12 13:38 UTCGHSA enrichment
  3. 2026-09-12 02:04 UTCEG score recompute
  4. 2026-09-12 02:04 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:30 UTCEG score recompute
  8. 2026-09-11 14:30 UTCGHSA enrichment
  9. 2026-09-11 02:56 UTCGHSA enrichment
  10. 2026-09-10 15:22 UTCEG score recompute
  11. 2026-09-10 15:22 UTCGHSA enrichment
  12. 2026-09-10 15:00 UTCEG score recompute
  13. 2026-09-10 15:00 UTCGHSA enrichment
  14. 2026-09-10 08:26 UTCGHSA enrichment
  15. 2026-09-09 20:50 UTCEG score recompute
  16. 2026-09-09 20:50 UTCGHSA enrichment
  17. 2026-09-09 12:25 UTCEG score recompute
  18. 2026-09-09 11:30 UTCEG score recompute
  19. 2026-09-09 11:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87817?
CVE-2026-87817 is a high vulnerability published on September 9, 2026. 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…
When was CVE-2026-87817 disclosed?
CVE-2026-87817 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87817 actively exploited?
CVE-2026-87817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2026-87817?
CVE-2026-87817 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-87817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87817, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-87817

Explore →

Is Your Infrastructure Affected by CVE-2026-87817?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.