CVE-2026-76217

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-62458 (ENISA EUVD) · GHSA-hh9p-6wh2-4mfc (GitHub Security Advisories) · GHSA-w672-239g-c3gr (GitHub Security Advisories) · PYSEC-2026-3841 (OSV.dev)Source: ENISA EUVD

6.5EG
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: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents returned in GitCommandError.stderr.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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
35th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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-10-31). 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 Arbitrary File Read via pathspec-from-file | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-read-via-pathspec-from-file
GitHub advisoryMentions a patch (unverified)

Arbitrary file read via --pathspec-from-file in IndexFile.remove() and Head.checkout() · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-hh9p-6wh2-4mfc

Vendor Advisories for CVE-2026-76217(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipGitPython @ 3.1.58 (fixes <= 3.1.57)—ghsa

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(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 145 refreshes 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 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-76217?
CVE-2026-76217 is a medium-severity vulnerability; its CVE record was published on August 19, 2026. GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). Attackers can supply --pathspec-from-file and --pathspec-file-nul parameters to read arbitrary files accessible to the process, with full file contents…
When was CVE-2026-76217 made public?
CVE-2026-76217 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-76217 actively exploited?
CVE-2026-76217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76217?
CVE-2026-76217 has a CVSS base score of 6.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-76217?
A fix for CVE-2026-76217 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76217 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-76217

Explore →

Is Your Infrastructure Affected by CVE-2026-76217?

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