CVE-2026-76219

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH 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 — 4 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
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
20%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 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(1)

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

Affected Packages

(1 across 1 ecosystem)
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 13× in last 7d / 13× 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.

  1. 2026-08-21 04:29 UTCEG score recompute
  2. 2026-08-21 04:29 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:38 UTCEG score recompute
  5. 2026-08-20 16:38 UTCGHSA enrichment
  6. 2026-08-20 15:45 UTCEG score recompute
  7. 2026-08-20 15:45 UTCGHSA enrichment
  8. 2026-08-20 14:15 UTCGHSA enrichment
  9. 2026-08-20 02:17 UTCEG score recompute
  10. 2026-08-20 02:17 UTCGHSA enrichment
  11. 2026-08-19 14:26 UTCEG score recompute
  12. 2026-08-19 14:12 UTCEG score recompute
  13. 2026-08-19 14:12 UTCMITRE cvelistV5first tracked

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 August 20, 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 79.8% 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