Skip to main content
VulnerabilityPublished Updated

CVE-2026-76217: GitPython · Arbitrary file read via --pathspec-from-file in IndexFile.remove() and Head.checkout()

Affects legitSource GCVE Database

0
Authoritative record:CVE-2026-76217· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.0.post0_14 soon.

Data as of 26 Oct 2026, 19:12 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.2.0.post0_14
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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. Weaponised: 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 26 Oct 2026.

What to do

Upgrade legit to 1.2.0.post0_14.

Affected software

ProductAffectedFixed in
Homebrewlegitpkg:brew/legitOther threatsAffected
  • >=0.1.0 <1.2.0.post0_14
Fixed in
  • 1.2.0.post0_14

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 1.2.0.post0_14 that addresses this issue. Users should upgrade to this version or later to remediate the vulnerability. Until patched, avoid passing untrusted input to the IndexFile.remove() and Head.checkout() methods with the --pathspec-from-file and --pathspec-file-nul options. No other mitigations are documented.

Description

GitPython versions >=0.1.0 and <1.2.0.post0_14 contain a vulnerability in the IndexFile.remove() and Head.checkout() methods. These methods forward arbitrary keyword arguments into git rm and git checkout commands without proper validation. When used with the --pathspec-from-file and --pathspec-file-nul options, this can cause Git to treat the entire contents of a specified file as a single pathspec, leading to the file's contents being leaked in error messages returned by GitPython. This allows an attacker with limited privileges to read arbitrary files on the system through error output.

References

Community reviews

Loading reviews…