CVSS 4.0
7.3 highCVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NHigh (7.3) in gitpython project gitpython. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in gitpython 3.1.53.
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:Hgitpython (PyPI): fixed in 3.1.53Explain CVE-2026-69097 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69097?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69097?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69097 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| gitpython-developers GitPython | before 3.1.53 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3rp5-jjmw-4wv2 | PyPI | gitpython | <3.1.53 | 3.1.53 |
| PYSEC-2026-3981 | PyPI | gitpython | <3.1.53 | 3.1.53 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | python-git | 3.1.30-1+deb12u3 | DEBIAN-CVE-2026-69097 |
| Debian | 13 | python-git | 3.1.44-1+deb13u1 | DEBIAN-CVE-2026-69097 |
| Debian | 14 | python-git | 3.1.61-1 | DEBIAN-CVE-2026-69097 |
| Ubuntu | 26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 more | python-git | no fix listed | UBUNTU-CVE-2026-69097 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 more | python-GitPython | 3.1.34.1693646983.2a2ae77-150400.9.8.1 | SUSE-SU-2026:4072-1 |
| openSUSE | Leap 16.0 | python-GitPython | 3.1.44-160000.4.1 | openSUSE-SU-2026:21874-1 |
| openSUSE | Tumbleweed | python-GitPython | 3.1.58-1.1 | openSUSE-SU-2026:11466-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Moderate.
Moderate: This flaw in GitPython allows for remote code execution within Red Hat products that utilize GitPython to process Git repositories. An attacker could inject arbitrary Git configuration directives, such as `core.sshCommand`, by crafting malicious submodule names. This occurs when a user performs `create_submodule` or `clone_from` operations on an untrusted repository, leading to code execution during subsequent Git SSH operations.
To mitigate this issue, users should avoid cloning or creating submodules from untrusted Git repositories. Exercise caution when interacting with Git repositories from unknown or unverified sources, as processing malicious submodule names can lead to configuration injection and potential remote code execution. Always ensure the integrity and trustworthiness of Git repositories before performing operations that involve submodule creation or cloning.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI 2.25 | rhoai/odh-feature-server-rhel9:1792148523 | Fixed 2026-10-21 | RHSA-2026:87410 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:1792563127 | Fixed 2026-10-21 | RHSA-2026:87410 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-th06-cpu-torch210-py312-rhel9:1791874335 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-th06-cuda130-torch210-py312-rhel9:1791961113 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-th06-rocm64-torch291-py312-rhel9:1791872119 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-training-cuda128-torch29-py312-rhel9:1791786619 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1791556128 | Fixed 2026-10-19 | RHSA-2026:84734 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1792721265 | Fixed 2026-10-29 | RHSA-2026:92510 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9:1792721112 | Fixed 2026-10-29 | RHSA-2026:92510 |
| Red Hat OpenShift AI 3.4 | rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1792721273 | Fixed 2026-10-29 | RHSA-2026:92510 |
| Exploit Intelligence | exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 | Not affected | |
| Exploit Intelligence | exploit-intelligence/vulnerability-analysis-rhel9 | Not affected | |
| Migration Toolkit for Applications 8 | mta/mta-solution-server-rhel9 | Not affected | |
| Pen Drive Powered by Red Hat Lightspeed | pen-drive/pen-drive-scanner-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-cpu-rhel9 | Not affected | |
| Red Hat AI Inference Server | rhaiis/vllm-tpu-rhel9 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/controller-rhel8 | Will not fix | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/hub-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/controller-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/hub-rhel8 | Not affected | |
| 74 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-69097.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37).