CVE-2026-78675

CVE-2026-78675 is a high-severity vulnerability in Gitpython Project Gitpython with a CVSS 3.x base score of 8.4. 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-73.

Key facts

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.

Frequently asked questions

What is CVE-2026-78675?
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.
How severe is CVE-2026-78675?
CVE-2026-78675 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-78675 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-78675?
CVE-2026-78675 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-78675?
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-78675 published?
CVE-2026-78675 was published on 2026-08-25 and last updated on 2026-09-02.

References

Affected products (1)

More vulnerabilities in Gitpython Project Gitpython

All CVEs affecting Gitpython Project Gitpython →

Other CWE-73 vulnerabilities

Browse all CWE-73 vulnerabilities →