CVE-2026-78677

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: github.
Web page

GitPython before 3.1.59 Path Traversal via separate-git-dir | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-path-traversal-via-separate-git-dir
GitHub advisoryMentions a patch (unverified)

clone_from()/clone() omit --separate-git-dir from unsafe_git_clone_options, enabling arbitrary git-directory creation outside the destination · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-8mcc-hrx5-hvxc

Vendor Advisories for CVE-2026-78677(7)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsatellite/iop-vmaas-rhel9:17913369552026-10-08redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17913404122026-10-08redhat
redhatsatellite/iop-vmaas-rhel9:17908200702026-10-08redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17913413682026-10-08redhat
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 18× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 126 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-78677?
CVE-2026-78677 is a high-severity vulnerability; its CVE record was published on August 25, 2026. GitPython before 3.1.59 omits --separate-git-dir from unsafegitcloneoptions, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separategitdir parameter to Repo.clonefrom() or Repo.clone() to redirect repository metadata to an…
When was CVE-2026-78677 made public?
CVE-2026-78677 was made public on August 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-78677 actively exploited?
CVE-2026-78677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78677?
CVE-2026-78677 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78677?
A fix for CVE-2026-78677 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78677 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-78677

Explore →

Is Your Infrastructure Affected by CVE-2026-78677?

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

Book a Demo →Browse All CVEs