CVE-2026-78679

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

GitPython before 3.1.59 contains an arbitrary file read vulnerability in TagReference.create() where a positional reference parameter bypasses the unsafe option guard. Attackers can supply a reference value like --file= to read arbitrary files, with contents returned in the annotated tag message.

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 computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.59 Arbitrary File Read via TagReference.create | Advisories | VulnCheck

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

TagReference.create positional reference bypasses kwargs-only --file guard, enabling arbitrary file read (incomplete fix of 3af0c251) · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-3wxw-xv34-2frg

Vendor Advisories for CVE-2026-78679(3)

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.el9ap2026-08-24redhat

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 (111 versions)3.1.59—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 66× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 08:55 UTCEG score recompute
  3. 2026-09-18 08:55 UTCVendor advisory
  4. 2026-09-17 08:13 UTCEG score recompute
  5. 2026-09-17 08:13 UTCVendor advisory
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 07:29 UTCEG score recompute
  8. 2026-09-16 07:29 UTCVendor advisory
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 06:47 UTCEG score recompute
  11. 2026-09-15 06:47 UTCVendor advisory
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 06:05 UTCEG score recompute
  15. 2026-09-14 06:05 UTCVendor advisory
  16. 2026-09-13 05:22 UTCEG score recompute
  17. 2026-09-13 05:22 UTCVendor advisory
  18. 2026-09-12 04:40 UTCEG score recompute
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 03:57 UTCEG score recompute
  22. 2026-09-09 02:33 UTCEG score recompute
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-08 01:50 UTCEG score recompute
  25. 2026-09-08 01:50 UTCGHSA enrichment
Show 41 more
  1. 2026-09-07 01:08 UTCEG score recompute
  2. 2026-09-07 01:07 UTCGHSA enrichment
  3. 2026-09-06 13:48 UTCEPSS rescore
  4. 2026-09-06 00:25 UTCEG score recompute
  5. 2026-09-06 00:25 UTCGHSA enrichment
  6. 2026-09-04 23:43 UTCEG score recompute
  7. 2026-09-04 23:43 UTCGHSA enrichment
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-03 23:00 UTCGHSA enrichment
  10. 2026-09-02 22:17 UTCEG score recompute
  11. 2026-09-02 22:17 UTCGHSA enrichment
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 21:32 UTCEG score recompute
  14. 2026-09-01 21:32 UTCGHSA enrichment
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 20:50 UTCGHSA enrichment
  19. 2026-08-30 19:52 UTCEG score recompute
  20. 2026-08-30 19:52 UTCGHSA enrichment
  21. 2026-08-30 19:18 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-29 19:10 UTCEG score recompute
  25. 2026-08-29 19:10 UTCGHSA enrichment
  26. 2026-08-28 21:42 UTCEPSS rescore
  27. 2026-08-28 18:22 UTCGHSA enrichment
  28. 2026-08-27 17:36 UTCEG score recompute
  29. 2026-08-27 17:36 UTCGHSA enrichment
  30. 2026-08-27 17:14 UTCEG score recompute
  31. 2026-08-27 17:14 UTCGHSA enrichment
  32. 2026-08-27 14:25 UTCEPSS rescore
  33. 2026-08-27 03:47 UTCEG score recompute
  34. 2026-08-27 03:47 UTCGHSA enrichment
  35. 2026-08-26 14:47 UTCEPSS rescore
  36. 2026-08-26 03:05 UTCEG score recompute
  37. 2026-08-26 03:04 UTCGHSA enrichment
  38. 2026-08-25 13:49 UTCEPSS rescore
  39. 2026-08-25 02:19 UTCEG score recompute
  40. 2026-08-25 01:50 UTCEG score recompute
  41. 2026-08-25 01:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78679?
CVE-2026-78679 is a medium vulnerability published on August 25, 2026. GitPython before 3.1.59 contains an arbitrary file read vulnerability in TagReference.create() where a positional reference parameter bypasses the unsafe option guard. Attackers can supply a reference value like --file=<path> to read arbitrary files, with contents returned in the annotated tag…
When was CVE-2026-78679 disclosed?
CVE-2026-78679 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78679 actively exploited?
CVE-2026-78679 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 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-78679?
CVE-2026-78679 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-78679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78679, 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-78679

Explore →

Is Your Infrastructure Affected by CVE-2026-78679?

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

Start Free Scan →Browse All CVEs