CVE-2026-76219

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

GitPython versions before 3.1.58 contain an arbitrary file overwrite vulnerability in IndexFile.from_tree, IndexFile.reset, and IndexFile.merge_tree methods that append caller-influenced treeish strings to git read-tree without option validation or argument separation. Attackers can inject the --index-output option to overwrite arbitrary files with a valid git-index blob, destroying existing file content at attacker-controlled writable paths.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
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 Arbitrary File Overwrite via read-tree | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-overwrite-via-read-tree
github Patch Available🟡 PoC Available

Unguarded git read-tree option forwarding in IndexFile.from_tree/reset/merge_tree enables arbitrary file overwrite · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-4gmw-gg2m-w46p

Vendor Advisories for CVE-2026-76219(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 26× in last 7d / 123× 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 128 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-76219?
CVE-2026-76219 is a high vulnerability published on August 19, 2026. GitPython versions before 3.1.58 contain an arbitrary file overwrite vulnerability in IndexFile.fromtree, IndexFile.reset, and IndexFile.mergetree methods that append caller-influenced treeish strings to git read-tree without option validation or argument separation. Attackers can inject the…
When was CVE-2026-76219 disclosed?
CVE-2026-76219 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-76219 actively exploited?
CVE-2026-76219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.2% of all scored CVEs.
What is the CVSS score of CVE-2026-76219?
CVE-2026-76219 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-76219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76219, 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-76219

Explore →

Is Your Infrastructure Affected by CVE-2026-76219?

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

Start Free Scan →Browse All CVEs