CVE-2026-76218

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
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: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

GitPython before 3.1.58 contains a remote code execution vulnerability in Repo.init that forwards unsafe git options without validation. Attackers can supply a template parameter pointing to a directory with malicious git hooks that execute arbitrary code when git operations are performed on the initialized repository.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 3, 2026

Advisory Details (2)

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

GitPython before 3.1.58 Remote Code Execution via Repo.init | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-remote-code-execution-via-repo-init
github Patch Available🟡 PoC Available

Unguarded git option forwarding in Repo.init enables arbitrary command execution via --template clone hooks · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-9rj7-rf2p-w77r

Vendor Advisories for CVE-2026-76218(2)

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 / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
python-git3.1.30-1 ... 3.1.61-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-13.1.61-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (110 versions)3.1.58—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 126× 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 137 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-76218?
CVE-2026-76218 is a high vulnerability published on August 19, 2026. GitPython before 3.1.58 contains a remote code execution vulnerability in Repo.init that forwards unsafe git options without validation. Attackers can supply a template parameter pointing to a directory with malicious git hooks that execute arbitrary code when git operations are performed on the…
When was CVE-2026-76218 disclosed?
CVE-2026-76218 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76218 actively exploited?
CVE-2026-76218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.6% of all scored CVEs.
What is the CVSS score of CVE-2026-76218?
CVE-2026-76218 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-76218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76218, 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-76218

Explore →

Is Your Infrastructure Affected by CVE-2026-76218?

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

Start Free Scan →Browse All CVEs