CVE-2026-78675: GitPython before 3.1.59 Local File Content Disclosure via .gitmodules
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gitpython-developers GitPython 3.1.59.
Low priority for now. Upgrade to gitpython-developers GitPython 3.1.59 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 25, 2026
- Updated
- Oct 12, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-73
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gitpython project | gitpython | cpe:2.3:a:gitpython_project:gitpython |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
gitpython-developers GitPython
- 3.1.59not affected
- before 3.1.59affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gitpython project gitpythonbefore 3.1.59
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | py3-gitpython | before 3.1.61-r0 | 3.1.61-r0 |
| Debian:12 | python-git | before 3.1.30-1+deb12u3 | 3.1.30-1+deb12u3 |
| Debian:13 | python-git | before 3.1.44-1+deb13u1 | 3.1.44-1+deb13u1 |
| Debian:14 | python-git | before 3.1.61-1 | 3.1.61-1 |
| openSUSE:Leap 16.0 | python-GitPython | before 3.1.44-160000.4.1 | 3.1.44-160000.4.1 |
| PyPI | gitpython | before 3.1.59 | 3.1.59 |
Same product
gitpython project: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-24439Remote Code Execution (RCE)41Plan
- CVE-2026-42284GitPython: Unsafe option check validates multi_options before shlex.split transforms it39Monitor
- CVE-2023-40267GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from.39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-76222Aug 19, 2026 · GitPython before 3.1.58 Path Traversal via .gitmodules Submodule Name33Monitor
- ← EarlierCVE-2026-76221Aug 19, 2026 · GitPython before 3.1.58 Config Injection via option-name34Monitor
- Later →CVE-2026-78676Aug 25, 2026 · GitPython before 3.1.59 Remote Code Execution via Config Injection37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| gitpython-developers GitPython | 3.1.59 | Vendor (CNA) |
| alpine:py3-gitpython | 3.1.61-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:python-git | 3.1.30-1+deb12u3 · Debian:12 | Package registry (OSV) |
| debian:python-git | 3.1.44-1+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:python-git | 3.1.61-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-GitPython | 3.1.44-160000.4.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| PyPI:gitpython | 3.1.59 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Pig-Tailreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-762176 days apartGitPython before 3.1.58 Arbitrary File Read via pathspec-from-file28Monitor
- CVE-2026-7361912 days apartGitPython before 3.1.57 Arbitrary File Read via Repo.archive()28Monitor
Not on record for this CVE: patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.