Skip to main content
CVE-2026-76221VulnerabilityPublished Updated

standardebooks · GitPython: git-config OPTION-name injection via =/#/whitespace bypasses name validator, enabling forged

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-76221· High 8.7

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

Data as of 22 Nov 2026, 18:11 UTC

CVSS 4.0 base score
8.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:L/AT:N/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 applies the same strict validation checks to option names as to section names, rejecting unsafe characters such as '=', '#', ';', '[', ']', and whitespace. Users should upgrade to GitPython 4.1.0 or later to remediate this vulnerability. No additional mitigation steps are required if the upgrade is applied.

Description

GitPython versions prior to 4.1.0 contain a vulnerability in the config-name validator that allows injection of arbitrary git configuration directives via crafted option names. The validator fails to reject characters such as '=', '#', ';', '[', ']', and whitespace in option names, enabling attackers to forge config directives like core.sshCommand or core.hooksPath. This can lead to remote code execution (RCE) on subsequent git operations if an attacker controls the option name passed to the config writer.

References

Community reviews

Loading reviews…