Skip to main content
VulnerabilityPublished Updated

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

Affects cruftSource GCVE Database

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

Not known to be exploited · CVSS 7.1 High : upgrade to 2.16.0_14 soon.

Data as of 26 Oct 2026, 17:42 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.16.0_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 cruft to 2.16.0_14.

Affected software

ProductAffectedFixed in
Homebrewcruftpkg:brew/cruftOther threatsAffected
  • >=2.9.0 <2.16.0_14
Fixed in
  • 2.16.0_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 2.16.0_14 that fixes this vulnerability. Users should upgrade to version 2.16.0_14 or later to mitigate this issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-76217 is a vulnerability in GitPython where the methods IndexFile.remove() and Head.checkout() forward arbitrary keyword arguments to 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 an error message that includes the entire file content in the command's stderr output. This results in an arbitrary file read disclosure to the caller. The issue affects GitPython versions from 2.9.0 up to but not including 2.16.0_14 and has been fixed in version 2.16.0_14.

References

Community reviews

Loading reviews…