Skip to main content
VulnerabilityPublished Updated

CVE-2026-78676: GitPython · Dormant multi-line git-config values are corrupted into live injected directives (e.g

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-78676· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 4.1.0 as a priority.

Data as of 22 Nov 2026, 18:11 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade standardebooks to 4.1.0.

Affected software

ProductAffectedFixed in
Homebrewstandardebookspkg:brew/standardebooksOther threatsAffected
  • >=2.9.2 <4.1.0
Fixed in
  • 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in GitPython version 4.1.0 that fixes the re-serialization logic to safely handle multi-line config values and prevent injection of new directives. Users should upgrade to version 4.1.0 or later. Until then, avoid performing config writes with GitPython on repositories containing untrusted or suspicious multi-line config values. No other mitigations are documented.

Description

GitPython versions from 2.9.2 up to but not including 4.1.0 contain a critical vulnerability (CVE-2026-78676) in their git config parser. The issue arises from improper handling of multi-line git config values during re-serialization, causing dormant multi-line values to be corrupted into live injected directives. This can lead to arbitrary code execution via the core.hooksPath configuration, which is honored by git hook-triggering operations. The vulnerability is due to asymmetric input validation: unsafe characters are blocked only on write arguments but not on values read from disk and later rewritten. A fix is available in version 4.1.0.

References

Community reviews

Loading reviews…