CVE-2026-87818 gitpython-developers CVE debrief

Who should care

Defenders responsible for GitPython deployments, repository administrators, and security teams should assess exposure and verify remediation. They should also review GitPython documentation and changelogs to understand the vulnerability and its impact. Additionally, they should verify GitPython versions and restrict access to sensitive repositories to prevent exploitation.

Why it matters

CVE-2026-87818 allows attackers to read arbitrary filesystem paths as repository operands, potentially leading to sensitive information disclosure.

• Attackers can query local files to recover single-line secrets
• Content-dependent Boolean oracle can be created using --no-index and -I/--ignore-matching-lines
• Verification of GitPython versions and repository access controls is necessary

Technical summary

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. This vulnerability enables attackers to 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. The issue is addressed in GitPython version 3.1.60, which restricts the --no-index option and prevents attackers from exploiting this vulnerability.

Defensive priority

Defenders should prioritize verifying GitPython versions and restricting access to sensitive repositories.

Recommended defensive actions

• Verify GitPython version and upgrade to 3.1.60 or later
• Restrict access to sensitive repositories
• Monitor repository access and query logs
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional verification is needed to confirm affected versions and remediation. Further review of GitPython documentation and changelogs reveals that version 3.1.60 addresses the issue. Defenders should verify GitPython versions and restrict access to sensitive repositories. Evidence limits suggest that exploitation requires local access to the repository and that attackers can query local files to recover single-line secrets.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.