Secuno
ENNL
Book demo

CVE-2026-78675

Gitpython path traversal

8.4 HIGHPublic exploitEPSS 0.18%
  1. Published25 Aug 2026

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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Gitpython< 3.1.59

Remediation

Fixed in
Gitpython≥ 3.1.59

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-599768.1
ConvertX is a self-hosted file conversion service. Prior to 0.18.0, the ImageMagick…
CVE-2026-1058658.1
Payload is a free and open source headless content management system. In versions…
CVE-2026-976628.2
An argument injection issue in the diff scan operation in AWS security-agent-mcp-server…
CVE-2026-1032559.0
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1…
CVE-2026-159838.1
The Super Forms – Drag & Drop Form Builder plugin for WordPress is vulnerable to…
CVE-2026-192538.7
The Cache Enabler WordPress plugin before 1.8.17 does not validate a URL before using…

Frequently asked

Is CVE-2026-78675 being actively exploited?

CVE-2026-78675 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.18%.

How severe is CVE-2026-78675?

CVE-2026-78675 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.18% probability of exploitation.

Which products are affected by CVE-2026-78675?

Affected products include Gitpython.

How do I fix CVE-2026-78675?

Upgrade affected software to a fixed version, for example Gitpython 3.1.59 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-78675 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.