Skip to main content
CVE-2026-67326VulnerabilityPublished Updated

standardebooks · GitPython: Newline injection

Affects standardebooksSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-67326· High 7.3

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

Data as of 22 Nov 2026, 18:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 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 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 fix is available in GitPython version 3.0.4. Users should upgrade to this version or later to mitigate the vulnerability. The patch addresses the incomplete validation by properly handling newline characters in all parameters. No additional mitigations are required if the patch is applied.

Description

A vulnerability in GitPython allows an attacker to inject newline characters into the section parameter of the config_writer() set_value() method. This bypasses the patch for CVE-2026-42215, enabling arbitrary section headers to be written into the .git/config file. By injecting a forged [core] section with hooksPath pointing to an attacker-controlled directory, remote code execution (RCE) can occur when a git hook is triggered.

References

Community reviews

Loading reviews…