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.
CVE-2026-78675
HIGHPre-NVD 8.48.4—Trending — 4 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 8.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.4
- EG Score
- 8.4(high)
- EG Risk
- 54(Track*)EG Risk 54/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity84% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
GitPython before 3.1.59 Local File Content Disclosure via .gitmodules | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitpython-before-local-file-content-disclosure-via-gitmodulesgithub Patch Available🟡 PoC Available
Arbitrary local file content disclosure via [include] directive in untrusted .gitmodules (SubmoduleConfigParser never disables merge_includes) · Advisory · gitpython-developers/GitPython · GitHub
https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-7833-fr7j-v32qVendor Advisories for CVE-2026-78675(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 02:28 UTCEG score recompute
- 2026-08-26 02:28 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 13:22 UTCEG score recompute
- 2026-08-25 13:22 UTCGHSA enrichment
- 2026-08-25 13:16 UTCEG score recompute
- 2026-08-25 13:16 UTCGHSA enrichment
- 2026-08-25 02:19 UTCEG score recompute
- 2026-08-25 01:50 UTCEG score recompute
- 2026-08-25 01:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-73
- CVE-2022-24900EG 9.9EPSS p95CRITICAL
- CVE-2020-37080EG 9.8CRITICAL
- CVE-2023-4634EG 9.8EPSS p100CRITICAL
- CVE-2023-4191EG 9.8CRITICAL
- CVE-2022-39952EG 9.8EPSS p100CRITICAL
- CVE-2014-125059NVD 5.0EG 9.8CRITICAL
- CVE-2014-125044NVD 6.3EG 9.8CRITICAL
- CVE-2022-45213NVD 5.3EG 9.8CRITICAL
- CVE-2021-38477EG 9.8CRITICAL
- CVE-2020-1631NVD 8.8EG 9.8 KEVEPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-78675?
CVE-2026-78675 is a high vulnerability published on August 25, 2026. 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…
When was CVE-2026-78675 disclosed?
CVE-2026-78675 was first published in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78675 actively exploited?
CVE-2026-78675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-78675?
CVE-2026-78675 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-78675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78675
Is Your Infrastructure Affected by CVE-2026-78675?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.