CVE-2026-69097 GitPython before 3.1.53 Config Injection via Submodule Names

High 7.3 Published Updated

Attackers can achieve remote code execution by injecting malicious git config directives via submodule names in GitPython.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-69097?

CVE-2026-69097 is a high-severity code injection vulnerability in gitpython-developers GitPython, published on 3 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

GitPython before 3.1.53 fails to properly escape section names in git config files, allowing attackers to inject arbitrary configuration directives through malicious submodule names. Attackers can inject core.sshCommand or other dangerous config keys into the victim's .git/config via create_submodule or clone_from operations, achieving remote code execution when git performs ssh operations.

Weakness: CWE-74

Which versions are affected by CVE-2026-69097?

3 open source packages ship an affected version, including gitpython. It affects 1 product.

PackageAffectedFixed in
gitpython PyPIAll versions3.1.53
gitpython PyPIAll versions3.1.53
gitpython PyPIAll versions3.1.53

Products include Gitpython Project Gitpython.

How do I fix CVE-2026-69097?

Upgrade gitpython to 3.1.53 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-69097 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69097 exists.

Sources

Also known as DEBIAN-CVE-2026-69097, ECHO-6b19-bb0e-4e42, ECHO-6d73-52e6-3a0a, GHSA-3rp5-jjmw-4wv2, MINI-4fmj-jp92-65xp, MINI-4p3c-736m-4hgq and 10 more.

Is CVE-2026-69097 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free