CVE-2026-100689

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitPython before 3.1.62 does not validate the path field read from an untrusted .gitmodules file when updating submodules. While a prior fix (GHSA-hmq2-w58f-27jc) added Submodule._validated_name() to constrain the name field, and GitPython's own containment guard Submodule._to_relative_path() is applied in add() and move(), Submodule.update() derives the absolute checkout location from the raw path value without that guard. A .gitmodules entry containing directory traversal components (e.g., path = ../../../tmp/escaped) can therefore cause directories to be created via os.makedirs() outside the repository working tree, populated from the submodule URL on the clone path, and removed via shutil.rmtree() when force_remove is used. Exploitation requires an application flow that updates submodules at a non-HEAD commit (such as a historical-commit API); the common clone-then-update flow re-derives the path from a canonical tree lookup and is not affected. The issue is fixed in GitPython 3.1.62.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
27
EG Risk 27/100CISA SSVC

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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
Patch available. Sources: github.
generic

GitPython before 3.1.62 Path Traversal via gitmodules path | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-3.1.62-path-traversal-via-gitmodules-path
github Patch Available

Residual of GHSA-hmq2-w58f-27jc: the fix validates the `.gitmodules` **name** but the sibling **path** field still reaches `os.makedirs()` unguarded, although GitPython already owns the containment guard · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-59cr-6r3x-644w

Vendor Advisories for CVE-2026-100689(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 (114 versions)3.1.62—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 28× 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-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 11:00 UTCEG score recompute
  3. 2026-10-04 11:00 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 13:02 UTCEG score recompute
  6. 2026-10-03 13:01 UTCGHSA enrichment
  7. 2026-10-02 14:59 UTCEG score recompute
  8. 2026-10-02 14:59 UTCGHSA enrichment
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-10-01 17:00 UTCGHSA enrichment
  11. 2026-09-30 18:41 UTCEG score recompute
  12. 2026-09-30 18:41 UTCGHSA enrichment
  13. 2026-09-30 17:47 UTCEG score recompute
  14. 2026-09-30 17:47 UTCGHSA enrichment
  15. 2026-09-30 15:02 UTCEPSS rescore
  16. 2026-09-29 22:13 UTCEG score recompute
  17. 2026-09-29 22:13 UTCGHSA enrichment
  18. 2026-09-29 15:20 UTCEPSS rescore
  19. 2026-09-29 08:26 UTCEG score recompute
  20. 2026-09-29 08:26 UTCGHSA enrichment
  21. 2026-09-28 13:50 UTCEPSS rescore
  22. 2026-09-28 10:28 UTCEG score recompute
  23. 2026-09-28 10:28 UTCGHSA enrichment
  24. 2026-09-27 12:29 UTCEG score recompute
  25. 2026-09-27 12:29 UTCGHSA enrichment
Show 3 more
  1. 2026-09-26 14:31 UTCEG score recompute
  2. 2026-09-26 13:35 UTCEG score recompute
  3. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-100689?
CVE-2026-100689 is a medium vulnerability published on September 26, 2026. GitPython before 3.1.62 does not validate the path field read from an untrusted .gitmodules file when updating submodules. While a prior fix (GHSA-hmq2-w58f-27jc) added Submodule.validatedname() to constrain the name field, and GitPython's own containment guard Submodule.torelativepath() is applied…
When was CVE-2026-100689 disclosed?
CVE-2026-100689 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100689 actively exploited?
CVE-2026-100689 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100689?
CVE-2026-100689 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100689?
A fix for CVE-2026-100689 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100689 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100689?

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

Book a Demo →Browse All CVEs