CVE-2026-78676

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week
9.8EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.8%
EPSS %ILE
54th
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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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 Oct 13, 2026
Patch available. Sources: github.
Web page

GitPython before 3.1.59 Remote Code Execution via Config Injection | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-remote-code-execution-via-config-injection
GitHub advisoryMentions a patch (unverified)

Dormant multi-line git-config values are corrupted into live injected directives (e.g. core.hooksPath) on any unrelated GitConfigParser write, enabling RCE · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-284h-m62q-gf8w

Vendor Advisories for CVE-2026-78676(8)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-27/hub-rhel9:17912545552026-10-08redhat
redhatansible-automation-platform-25/controller-rhel8:17896070212026-09-23redhat
redhatansible-automation-platform-26/controller-rhel9:17896737392026-09-23redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat

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 26× in last 7d / 143× 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 100 of 269 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. None are among the latest 100 rows. The 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-78676?
CVE-2026-78676 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated…
When was CVE-2026-78676 made public?
CVE-2026-78676 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-78676 actively exploited?
CVE-2026-78676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78676?
CVE-2026-78676 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78676?
A fix for CVE-2026-78676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78676 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-78676

Explore →

Is Your Infrastructure Affected by CVE-2026-78676?

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

Book a Demo →Browse All CVEs