Skip to main content
CVE-2026-76218VulnerabilityPublished Updated

Repo.init enables arbitrary command execution · GitPython: Unguarded git option forwarding

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-76218· High 7.7

Not known to be exploited · CVSS 7.7 High : upgrade to 4.1.0 soon.

Data as of 22 Nov 2026, 18:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 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 adds a check_unsafe_options guard to Repo.init(), preventing unsafe options like --template and --separate-git-dir from being used without explicit allowance. Users should upgrade to version 4.1.0 or later. Until upgraded, avoid passing untrusted input to the template parameter in Repo.init() and do not allow attacker-controlled paths for git init options.

Description

GitPython's Repo.init() method forwards keyword arguments directly to git init without checking for unsafe options. This allows an attacker who can control the template directory path to plant malicious git hooks that execute arbitrary code during subsequent git operations. The vulnerability affects GitPython versions from 2.9.2 up to but not including 4.1.0. A fix is available in version 4.1.0 that adds checks to prevent unsafe options like --template and --separate-git-dir from being used without explicit allowance.

References

Community reviews

Loading reviews…