Skip to main content
VulnerabilityPublished Updated

CVE-2026-42284: GitPython · Unsafe option check validates multi_options before shlex.split transformation

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-42284· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 3.0.4 soon.

Data as of 22 Nov 2026, 18:22 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.0.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 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 3.0.4.

Affected software

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

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

AI-suggested

A fixed version of GitPython is available in 3.0.4. Users and applications should upgrade to GitPython 3.0.4 or later to remediate this vulnerability. Until upgraded, avoid passing user-controlled input to the multi_options parameter in clone_from(), clone(), or Submodule.update().

Description

GitPython versions from 2.9.2 up to but not including 3.0.4 contain a vulnerability in the handling of multi_options in the clone and submodule update functions. The vulnerability arises because validation is performed on the original list of options before they are split by shlex.split, allowing an attacker to embed unsafe options like '--config core.hooksPath=...' within a single string that passes validation but is split into multiple unsafe tokens at execution time. This can lead to execution of attacker-controlled Git hooks during repository cloning.

References

Community reviews

Loading reviews…