Skip to main content
CVE-2026-76222VulnerabilityPublished Updated

standardebooks · GitPython: Arbitrary Git Repository Creation Outside the Working Tree via Unvalidated .gitmodules Submodule Name in

Affects standardebooksSource GCVE Database

0
Compare
Authoritative record:CVE-2026-76222· High 8.4

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

Data as of 22 Nov 2026, 18:11 UTC

CVSS 4.0 base score
8.4High
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:N/UI:P/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L

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

Upgrade GitPython to version 4.1.0 or later, where this vulnerability is fixed. Avoid using vulnerable GitPython versions to clone and initialize submodules from untrusted repositories. No other mitigations are indicated by the vendor advisory.

Description

GitPython versions from 2.9.2 up to but not including 4.1.0 contain a vulnerability where an attacker-controlled submodule name in a cloned repository's .gitmodules file can cause GitPython to create and initialize a Git repository outside the intended working directory. This occurs because GitPython does not validate submodule names for path traversal sequences, allowing arbitrary filesystem paths for submodule Git directories. The vulnerability requires a victim to clone a malicious repository and run submodule initialization via GitPython. The issue is fixed in GitPython 4.1.0.

References

Community reviews

Loading reviews…