GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller.
CVE-2026-78678
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026GitPython before 3.1.59 Arbitrary File Read via Repo.blame() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-read-via-repo-blameIncomplete unsafe_git_revision_options denylist omits --contents/-S, enabling arbitrary file read via Repo.blame() · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-5xxx-qhh7-9287Vendor Advisories for CVE-2026-78678(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× 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.
- 2026-08-30 01:35 UTCGHSA enrichment
- 2026-08-29 00:18 UTCEG score recompute
- 2026-08-29 00:18 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 19:06 UTCEG score recompute
- 2026-08-27 19:06 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:46 UTCEG score recompute
- 2026-08-26 17:46 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 16:24 UTCEG score recompute
- 2026-08-25 16:24 UTCGHSA enrichment
- 2026-08-25 15:30 UTCEG score recompute
- 2026-08-25 15:30 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2007-0882EG 10.0EPSS p100HIGH
- CVE-2004-0480EG 10.0EPSS p95HIGH
- CVE-1999-0113EG 10.0EPSS p97HIGH
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS p95CRITICAL
- CVE-2020-21224EG 9.8EPSS p99CRITICAL
- CVE-2020-25494EG 9.8EPSS p99CRITICAL
- CVE-2020-15692EG 9.8EPSS p90CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS p100CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-78678?
When was CVE-2026-78678 disclosed?
Is CVE-2026-78678 actively exploited?
What is the CVSS score of CVE-2026-78678?
How do I remediate CVE-2026-78678?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78678
Is Your Infrastructure Affected by CVE-2026-78678?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.