Skip to main content
VulnerabilityPublished Updated

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

Affects mistral-vibeSource GCVE Database

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

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

Data as of 30 Oct 2026, 07:45 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.24.3
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. 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 29 Oct 2026.

What to do

Upgrade mistral-vibe to 2.24.3.

Affected software

ProductAffectedFixed in
Homebrewmistral-vibepkg:brew/mistral-vibeOther threatsAffected
  • >=2.1.0 <2.24.3
Fixed in
  • 2.24.3

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 2.24.3. Users should upgrade to version 2.24.3 or later to remediate this vulnerability. No additional mitigation steps are required once the patch is applied.

Description

GitPython versions from 2.1.0 up to but not including 2.24.3 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 option combined with --pathspec-file-nul, this causes Git to treat the entire file as a single NUL-delimited pathspec. If the pathspec does not match any files, the error message returned includes the full contents of the specified file, leading to arbitrary file read disclosure. This vulnerability has a CVSS score of 6.5 (medium severity) and is fixed in version 2.24.3.

References

Community reviews

Loading reviews…