NVD / CVE Program· CNA VulnCheck

CVE-2026-69097: GitPython before 3.1.53 Config Injection via Submodule Names

Noroxi assessment

Priority: Monitor (action score 29/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.26% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
Fixed version: gitpython-developers GitPython 3.1.53.

Low priority for now. Upgrade to gitpython-developers GitPython 3.1.53 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.53 fails to properly escape section names in git config files, allowing attackers to inject arbitrary configuration directives through malicious submodule names. Attackers can inject core.sshCommand or other dangerous config keys into the victim's .git/config via create_submodule or clone_from operations, achieving remote code execution when git performs ssh operations.

HighCVSS 7.3 · v4.0—No exploit Fix available

Published: Aug 3, 2026
Updated: Oct 23, 2026
EPSS: 0.2% · 18th percentile
CWE: CWE-74

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

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: 7.3; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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

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.53

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.53not affected
- before 3.1.53affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	python-git	from 0	—
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
openSUSE:Tumbleweed	python-GitPython	before 3.1.58-1.1	3.1.58-1.1
PyPI	gitpython	before 3.1.53	3.1.53
SUSE:Linux Enterprise Module for Python 3 15 SP7	python-GitPython	before 3.1.34.1693646983.2a2ae77-150400.9.8.1	3.1.34.1693646983.2a2ae77-150400.9.8.1

Same product

gitpython project: all records

Other 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 it
39Monitor
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-67325Aug 1, 2026 · GitPython before 3.1.51 Command Injection via option prefix abbreviation
35Monitor
← EarlierCVE-2026-67326Aug 1, 2026 · GitPython before 3.1.50 Newline Injection via config_writer section
29Monitor
Later →CVE-2026-73619Aug 13, 2026 · GitPython before 3.1.57 Arbitrary File Read via Repo.archive()
28Monitor

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.53	Vendor (CNA)
debian:python-git	3.1.61-1 · Debian:14	Package registry (OSV)
opensuse:python-GitPython	3.1.58-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
PyPI:gitpython	3.1.53	Package registry (OSV)
suse:python-GitPython	3.1.34.1693646983.2a2ae77-150400.9.8.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7	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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-7622116 days apartGitPython before 3.1.58 Config Injection via option-name
34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: High
Privileges required: None
User interaction: P
Scope: X

Weakness class (CWE)

CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

CVSS vector

CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/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)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.vulncheck.com/advisories/gitpython-before-config-injection-via-submodule-names

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records