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
- 15%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
September 2, 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.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.30-1 ... 3.1.61-1 (11 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-git | 3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1 | 3.1.61-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gitpython | 0.1.7 ... 3.1.9 (111 versions) | 3.1.59 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 59× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-18 14:25 UTCEG score recompute
- 2026-09-17 13:08 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 11:39 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 10:14 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 08:56 UTCEG score recompute
- 2026-09-13 07:39 UTCEG score recompute
- 2026-09-12 06:22 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 05:04 UTCEG score recompute
- 2026-09-09 02:30 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 01:12 UTCEG score recompute
- 2026-09-08 01:12 UTCGHSA enrichment
- 2026-09-06 23:54 UTCEG score recompute
- 2026-09-06 23:54 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-05 22:33 UTCEG score recompute
- 2026-09-05 22:33 UTCGHSA enrichment
- 2026-09-04 21:14 UTCEG score recompute
Show 34 moreShow fewer
- 2026-09-04 21:14 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 19:57 UTCGHSA enrichment
- 2026-09-02 18:39 UTCEG score recompute
- 2026-09-02 18:38 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 21:58 UTCEG score recompute
- 2026-09-01 21:58 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 20:41 UTCGHSA enrichment
- 2026-08-31 02:52 UTCEG score recompute
- 2026-08-31 02:52 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 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
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
See which npm, PyPI, Go, and Maven packages are affected by 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.