CVE-2026-78679

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. The CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
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.3%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

October 8, 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
githubMentions a patch (unverified)🟡 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(15)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-gitpython-0:3.1.62-1.el9pc2026-10-01redhat
redhatpython3.12-gitpython-0:3.1.62-1.el9pc2026-10-01redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17908212172026-10-01redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17908208212026-10-01redhat
redhatansible-automation-platform-26/hub-rhel9:17896112742026-09-23redhat
redhatautomation-controller-0:4.7.17-1.el9ap2026-09-23redhat
redhatansible-automation-platform-27/hub-rhel9:17895726322026-09-23redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatansible-automation-platform-27/controller-rhel9:17889183632026-09-14redhat
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 rangeFix by version rangeDependents
python-git3.1.30-1 ... 3.1.62-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1 ... 3.1.62-2 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1
  • every version up to 3.1.61-1: fixed in 3.1.61-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython0.1.7 ... 3.1.9 (111 versions)
  • every version up to 3.1.59: fixed in 3.1.59
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 78× 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 123 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 on August 25, 2026, with the most recent update on October 8, 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.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78679?
CVE-2026-78679 has a CVSS base score of 6.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-78679?
A fix for CVE-2026-78679 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78679 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs