6.5Medium
Gitpython Project Gitpython
CVE-2026-87818
GitPython 3.1.59 fails to restrict the --no-index option in the high-level diff API, allowing attackers to read arbitrary filesystem paths as repository operands. Attackers can combine --no-index with -I/--ignore-matching-lines to create a content-dependent Boolean oracle, repeatedly querying local files to recover single-line secrets through distinguishable success or error responses.
What this means for your business
- It affects Gitpython Project Gitpython. It matters if your company, or a supplier that handles your data, runs it.
- Code showing how to exploit it has been published, but real attacks have not been confirmed.
- An attacker can use it remotely, over a network, with an ordinary user login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.2% chance of attack attempts being seen in the next 30 days, ranking above 13% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Gitpython Project Gitpython, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 6.5 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- CVSS v4
- 7.1
- Weakness
- CWE-88
- Assigned by
- disclosure@vulncheck.com
Dates
- Published
- 2026-09-09
- Last modified
- 2026-09-16
- Sources
- NVD
Affected products
- Gitpython Project Gitpython- 3.1.60
As listed in the NVD configuration data. Not a statement about your estate.