CVE-2026-87817

gitpython is a software component that lets an application work with code repositories. This flaw is like a delivery box with a hidden instruction that makes a staff member unlock a side door when they file its contents: a harmful repository can cause your system to run an attacker's command when it saves a change.

This matters to you if your business runs applications that use gitpython to open, clone, or manage code repositories. It is especially relevant for build systems, developer tools, or services that handle repositories from customers or other outside sources. The risk requires an application to commit changes to a malicious cloned or opened repository.

An attacker can trigger code execution when a vulnerable application commits to a malicious repository, so schedule this update promptly. There is no record of active exploitation or public exploit code, which supports an AMBER priority rather than an emergency response.

1. Identify deployed Python environments that import gitpython, including CI/CD workers, internal developer tools, and services that clone or open repositories.
2. Confirm whether those environments can receive repositories or repository contents from untrusted sources and whether they call index.commit().
3. Upgrade each affected deployment to gitpython 3.1.60, then run the application's normal repository and commit tests before releasing it.
4. If upgrading is delayed, block commits against untrusted repositories and run any unavoidable repository processing in an isolated, non-production environment with minimal permissions.
5. Review logs and audit trails for automated commits involving externally supplied repositories, especially for unexpected child processes, hook activity, or changes made by the service account.
6. No CISA KEV remediation due date applies because this CVE is not listed in the CISA KEV catalog.

CVSS v3.1 is 8.8 (HIGH): AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The issue is CWE-94 and stems from insufficient validation of git-directory location metadata, including tracked gitdir, commondir, and HEAD files; an attacker can redirect GitPython to a malicious tracked hooks directory whose pre-commit hook executes on index.commit(). CISA KEV does not list this CVE, and no public exploit code is on record. EPSS is 0.3% (26th percentile) with a flat trend; this is a prediction, not evidence of exploitation.