CVE-2026-76222

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal sequences in submodule names that GitPython processes during submodule initialization, creating attacker-controlled Git repositories at escaped filesystem locations.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

August 19, 2026

Last Modified

September 2, 2026

Advisory Details (2)

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

GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-path-traversal-via-gitmodules-submodule-name
github Patch Available🟡 PoC Available

Arbitrary Git Repository Creation Outside the Working Tree via Unvalidated .gitmodules Submodule Name in GitPython · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-hmq2-w58f-27jc

Vendor Advisories for CVE-2026-76222(10)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatansible-automation-platform-27/controller-rhel9:17895806842026-09-23redhat
redhatansible-automation-platform-26/controller-rhel9:17896737392026-09-23redhat
redhatrhoai/odh-training-cuda128-torch29-py312-rhel9:17895298512026-09-21redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat
redhatpython3.12-gitpython-0:3.1.59-1.el9pc2026-09-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.30-1 ... 3.1.62-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1 ... 3.1.62-2 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1
  • every version up to 3.1.61-1: fixed in 3.1.61-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython0.1.7 ... 3.1.9 (110 versions)
  • every version up to 3.1.58: fixed in 3.1.58
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 111× 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.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-10-05 09:33 UTCEG score recompute
  2. 2026-10-05 09:33 UTCVendor advisory
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 21:26 UTCVendor advisory
  5. 2026-10-04 05:08 UTCVendor advisory
  6. 2026-10-03 16:58 UTCEG score recompute
  7. 2026-10-03 16:58 UTCVendor advisory
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 00:42 UTCEG score recompute
  10. 2026-10-03 00:42 UTCVendor advisory
  11. 2026-10-02 11:08 UTCVendor advisory
  12. 2026-10-01 22:48 UTCEG score recompute
  13. 2026-10-01 22:48 UTCVendor advisory
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 08:36 UTCVendor advisory
  16. 2026-09-30 20:41 UTCEG score recompute
  17. 2026-09-30 20:41 UTCVendor advisory
  18. 2026-09-30 08:50 UTCEG score recompute
  19. 2026-09-30 08:50 UTCVendor advisory
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-28 21:44 UTCEG score recompute
  22. 2026-09-28 21:44 UTCVendor advisory
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 06:48 UTCVendor advisory
  25. 2026-09-27 18:56 UTCEG score recompute
Show 75 more
  1. 2026-09-27 18:56 UTCVendor advisory
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-27 07:05 UTCEG score recompute
  4. 2026-09-27 07:05 UTCVendor advisory
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-26 00:28 UTCEPSS rescore
  7. 2026-09-25 12:44 UTCVendor advisory
  8. 2026-09-25 00:54 UTCEG score recompute
  9. 2026-09-25 00:54 UTCVendor advisory
  10. 2026-09-24 14:04 UTCEPSS rescore
  11. 2026-09-24 11:26 UTCVendor advisory
  12. 2026-09-23 23:35 UTCEG score recompute
  13. 2026-09-23 23:35 UTCVendor advisory
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 11:44 UTCVendor advisory
  16. 2026-09-22 23:54 UTCEG score recompute
  17. 2026-09-22 23:54 UTCVendor advisory
  18. 2026-09-22 16:01 UTCEPSS rescore
  19. 2026-09-22 12:03 UTCVendor advisory
  20. 2026-09-22 00:13 UTCEG score recompute
  21. 2026-09-22 00:13 UTCVendor advisory
  22. 2026-09-21 21:09 UTCEPSS rescore
  23. 2026-09-21 12:20 UTCVendor advisory
  24. 2026-09-21 00:29 UTCEG score recompute
  25. 2026-09-21 00:29 UTCVendor advisory
  26. 2026-09-20 20:16 UTCEPSS rescore
  27. 2026-09-20 12:38 UTCVendor advisory
  28. 2026-09-20 00:27 UTCEG score recompute
  29. 2026-09-20 00:27 UTCVendor advisory
  30. 2026-09-19 12:36 UTCVendor advisory
  31. 2026-09-19 00:44 UTCEG score recompute
  32. 2026-09-19 00:44 UTCVendor advisory
  33. 2026-09-18 19:28 UTCEPSS rescore
  34. 2026-09-18 12:53 UTCVendor advisory
  35. 2026-09-18 01:02 UTCEG score recompute
  36. 2026-09-18 01:02 UTCVendor advisory
  37. 2026-09-17 13:11 UTCVendor advisory
  38. 2026-09-17 00:33 UTCEG score recompute
  39. 2026-09-17 00:33 UTCVendor advisory
  40. 2026-09-16 14:08 UTCEPSS rescore
  41. 2026-09-16 12:42 UTCEG score recompute
  42. 2026-09-16 12:42 UTCVendor advisory
  43. 2026-09-16 05:15 UTCEPSS rescore
  44. 2026-09-16 00:51 UTCVendor advisory
  45. 2026-09-15 12:59 UTCEG score recompute
  46. 2026-09-15 12:59 UTCVendor advisory
  47. 2026-09-15 03:12 UTCEPSS rescore
  48. 2026-09-15 01:08 UTCVendor advisory
  49. 2026-09-14 13:17 UTCVendor advisory
  50. 2026-09-14 01:26 UTCEG score recompute
  51. 2026-09-14 01:26 UTCVendor advisory
  52. 2026-09-13 13:35 UTCVendor advisory
  53. 2026-09-13 01:44 UTCEG score recompute
  54. 2026-09-13 01:44 UTCVendor advisory
  55. 2026-09-12 15:02 UTCEPSS rescore
  56. 2026-09-12 13:53 UTCVendor advisory
  57. 2026-09-12 02:02 UTCEG score recompute
  58. 2026-09-12 02:02 UTCVendor advisory
  59. 2026-09-11 14:53 UTCEPSS rescore
  60. 2026-09-11 14:11 UTCEG score recompute
  61. 2026-09-11 14:11 UTCVendor advisory
  62. 2026-09-11 02:20 UTCVendor advisory
  63. 2026-09-10 14:29 UTCEG score recompute
  64. 2026-09-10 14:29 UTCVendor advisory
  65. 2026-09-10 09:35 UTCEPSS rescore
  66. 2026-09-10 02:39 UTCVendor advisory
  67. 2026-09-09 14:47 UTCVendor advisory
  68. 2026-09-09 02:40 UTCEG score recompute
  69. 2026-09-09 02:40 UTCVendor advisory
  70. 2026-09-08 22:01 UTCEPSS rescore
  71. 2026-09-08 06:43 UTCVendor advisory
  72. 2026-09-08 06:43 UTCGHSA enrichment
  73. 2026-09-07 18:52 UTCEG score recompute
  74. 2026-09-07 18:52 UTCVendor advisory
  75. 2026-09-07 18:52 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-76222?
CVE-2026-76222 is a high vulnerability published on August 19, 2026. GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory. Attackers can craft malicious repositories with traversal sequences in submodule names that GitPython…
When was CVE-2026-76222 disclosed?
CVE-2026-76222 was first published on August 19, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76222 actively exploited?
CVE-2026-76222 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76222?
CVE-2026-76222 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76222?
A fix for CVE-2026-76222 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76222 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-76222

Explore →

Is Your Infrastructure Affected by CVE-2026-76222?

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

Book a Demo →Browse All CVEs