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.8% (55th percentile of EPSS-scored CVEs). 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: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 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.8%
EPSS %ILE
55th
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 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(9)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-26/controller-rhel9:17896737392026-09-23redhat
redhatansible-automation-platform-27/controller-rhel9:17895806842026-09-23redhat
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-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 21× in last 7d / 107× 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 189 total refreshes for this CVE.

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

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

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 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 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-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?
A fix for CVE-2026-76218 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76218 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-76218

Explore →

Is Your Infrastructure Affected by CVE-2026-76218?

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

Book a Demo →Browse All CVEs