Skip to main content
CVE-2026-67323VulnerabilityPublished Updated

standardebooks · GitPython: command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-67323· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade to 4.0.2 soon.

Data as of 22 Nov 2026, 18:22 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.0.2
CVSS:4.0/AV:L/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 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 4.0.2.

Affected software

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

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

AI-suggested

Upgrade GitPython to version 4.0.2 or later, where the issue is fixed. Avoid using untrusted input to construct Git command options in affected methods. Since a patch is available, applying the official fix is the recommended mitigation.

Description

GitPython versions from 2.9.2 up to but not including 4.0.2 contain command injection vulnerabilities in the Repo.archive(), git.ls_remote(), and other Git command wrappers. These vulnerabilities arise from insufficient validation of user-supplied options that are passed directly to Git commands, allowing execution of arbitrary commands or unintended file truncation. The issue is fixed in version 4.0.2.

References

Community reviews

Loading reviews…