CVE-2026-76222

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. The CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-62463 (ENISA EUVD) · GHSA-3vrx-526r-64rm (GitHub Security Advisories) · GHSA-hmq2-w58f-27jc (GitHub Security Advisories) · PYSEC-2026-3784 (OSV.dev)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: No code on recordExposed 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Aug 19, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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

Patch Availability(14)

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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
py3-gitpython—
  • every version up to 3.1.61-r0: fixed in 3.1.61-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.30-1, 3.1.30-1+deb12u2
  • every version up to 3.1.30-1+deb12u3: fixed in 3.1.30-1+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1
  • every version up to 3.1.44-1+deb13u1: fixed in 3.1.44-1+deb13u1
—
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(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 257 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-13 05:44 UTCEchelonGraph re-scored
  3. 2026-11-13 05:44 UTCVendor advisory
  4. 2026-11-13 05:44 UTCGHSA enrichmentGHSA-hmq2-w58f-27jc · GitHub severity HIGH · GitHub CVSS 8.2
  5. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-11-05 14:00 UTCEchelonGraph re-scored
  14. 2026-11-05 14:00 UTCVendor advisory
  15. 2026-11-05 14:00 UTCGHSA enrichmentGHSA-hmq2-w58f-27jc · GitHub severity HIGH · GitHub CVSS 8.2
  16. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-11-01 07:39 UTCGHSA enrichmentGHSA-hmq2-w58f-27jc · GitHub severity HIGH · GitHub CVSS 8.2
  21. 2026-11-01 07:39 UTCEchelonGraph re-scored
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-28 22:16 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-28 22:16 UTCVendor advisory
  2. 2026-10-28 19:55 UTCOSV refresh
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-25 14:02 UTCEchelonGraph re-scored
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-20 22:54 UTCEchelonGraph re-scored
  13. 2026-10-20 22:54 UTCVendor advisory
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-18 03:13 UTCEchelonGraph re-scored
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-13 07:10 UTCEchelonGraph re-scored
  24. 2026-10-13 07:10 UTCVendor advisory
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-10-12 15:38 UTCEchelonGraph re-scored
  27. 2026-10-11 19:24 UTCEchelonGraph re-scored
  28. 2026-10-11 16:40 UTCEchelonGraph re-scored
  29. 2026-10-11 13:59 UTCEchelonGraph re-scored
  30. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-10-08 15:42 UTCEchelonGraph re-scored
  35. 2026-10-08 15:42 UTCVendor advisory
  36. 2026-10-08 08:36 UTCEchelonGraph re-scored
  37. 2026-10-08 08:36 UTCVendor advisory
  38. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-10-07 10:29 UTCVendor advisory
  40. 2026-10-06 21:23 UTCEchelonGraph re-scored
  41. 2026-10-06 21:23 UTCVendor advisory
  42. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-10-06 08:00 UTCEchelonGraph re-scored
  44. 2026-10-06 08:00 UTCVendor advisory
  45. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-10-05 09:33 UTCEchelonGraph re-scored
  47. 2026-10-05 09:33 UTCVendor advisory
  48. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-10-04 21:26 UTCVendor advisory
  50. 2026-10-04 05:08 UTCVendor advisory
  51. 2026-10-03 16:58 UTCEchelonGraph re-scored
  52. 2026-10-03 16:58 UTCVendor advisory
  53. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-10-03 00:42 UTCEchelonGraph re-scored
  55. 2026-10-03 00:42 UTCVendor advisory
  56. 2026-10-02 11:08 UTCVendor advisory
  57. 2026-10-01 22:48 UTCEchelonGraph re-scored
  58. 2026-10-01 22:48 UTCVendor advisory
  59. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-10-01 08:36 UTCVendor advisory
  61. 2026-09-30 20:41 UTCEchelonGraph re-scored
  62. 2026-09-30 20:41 UTCVendor advisory
  63. 2026-09-30 08:50 UTCEchelonGraph re-scored
  64. 2026-09-30 08:50 UTCVendor advisory
  65. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  66. 2026-09-28 21:44 UTCEchelonGraph re-scored
  67. 2026-09-28 21:44 UTCVendor advisory
  68. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  69. 2026-09-28 06:48 UTCVendor advisory
  70. 2026-09-27 18:56 UTCEchelonGraph re-scored
  71. 2026-09-27 18:56 UTCVendor advisory
  72. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  73. 2026-09-27 07:05 UTCEchelonGraph re-scored
  74. 2026-09-27 07:05 UTCVendor advisory
  75. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2026-76222?
CVE-2026-76222 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-76222 was made public on August 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
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 (37th 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 (the CNA's own assessment, by vulncheck; 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.