How severe is CVE-2026-87817?

CVE-2026-87817 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-87817 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-87817?

CVE-2026-87817 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-87817?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-87817 published?

CVE-2026-87817 was published on 2026-09-09 and last updated on 2026-09-16.

CVE-2026-87817

CVE-2026-87817 is a high-severity vulnerability in Gitpython Project Gitpython with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-94.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v4: 8.7
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-94
Affected product: Gitpython Project Gitpython
Published: 2026-09-09
Last modified: 2026-09-16

Description

GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.

Frequently asked questions

What is CVE-2026-87817?: GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.
How severe is CVE-2026-87817?: CVE-2026-87817 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-87817 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-87817?: CVE-2026-87817 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-87817?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-87817 published?: CVE-2026-87817 was published on 2026-09-09 and last updated on 2026-09-16.

References

Affected products (1)

cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*

More vulnerabilities in Gitpython Project Gitpython

CVE-2026-78676 — Critical (CVSS 9.8): GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting…
CVE-2026-67324 — Critical (CVSS 9.8): GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of…
CVE-2023-40267 — Critical (CVSS 9.8): GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from. NOTE: this issue exists…
CVE-2026-76221 — High (CVSS 8.8): GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows…
CVE-2026-76220 — High (CVSS 8.8): GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be…
CVE-2026-73625 — High (CVSS 8.8): GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that…

All CVEs affecting Gitpython Project Gitpython →

Other CWE-94 (Code Injection) vulnerabilities

CVE-2026-105857 — Critical (CVSS 10.0): Payload is a free and open source headless content management system. In @payloadcms/plugin-form-builder versions…
CVE-2026-55107 — Critical (CVSS 10.0): Kobako is a Ruby gem that embeds a Wasm-isolated mruby interpreter inside applications, allowing execution of untrusted…
CVE-2026-96349 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in SiteSkite <= 2.1.8 versions.
CVE-2026-102425 — Critical (CVSS 10.0): Joomla Extension - balbooa.com - Unauthenticated RCE via field shortcode injection in Balbooa Forms < 2.4.3.4 - Balbooa…
CVE-2026-89275 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability…
CVE-2026-84412 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability…

Browse all CWE-94 (Code Injection) vulnerabilities →