CVE-2026-78675 GitPython before 3.1.59 Local File Content Disclosure via .gitmodules

High 8.6 Published Updated

Attackers can disclose local file contents by crafting malicious .gitmodules files, exposing sensitive data via exception messages in GitPython.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-78675?

CVE-2026-78675 is a high-severity vulnerability in gitpython-developers GitPython, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file's first line verbatim in the exception message.

Weakness: CWE-73

Which versions are affected by CVE-2026-78675?

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

PackageAffectedFixed in
gitpython PyPIAll versions3.1.59
gitpython PyPIAll versions3.1.59
GitPython PyPIAll versions3.1.59

Products include Gitpython Project Gitpython.

How do I fix CVE-2026-78675?

Upgrade gitpython to 3.1.59 or later.

Is CVE-2026-78675 being exploited?

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

Sources

Also known as DEBIAN-CVE-2026-78675, ECHO-c442-4553-3c14, GHSA-7833-fr7j-v32q, MINI-6r37-3r7g-v79x, MINI-7wg4-wmw3-242x, MINI-rv63-j652-rx47 and 3 more.

Is CVE-2026-78675 in your software?

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

Check your SBOMs for free