Secuno
ENNL
Book demo

CVE-2026-69097

7.0 HIGHPublic exploitEPSS 0.29%
  1. Published3 Aug 2026

Description

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.

CVSS 3.1 breakdown

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

Affected products

Gitpython Project Gitpython< 3.1.53

Remediation

Fixed in
Gitpython Project Gitpython≥ 3.1.53

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-2013010.0
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-123558.1
IBM MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through…
CVE-2026-123519.8
IBM MQ 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through…
CVE-2026-875728.3
Injection in DevTools in Google Chrome prior to 153.0.8010.36 allowed a remote attacker…
CVE-2026-656699.6
Improper neutralization of special elements in output used by a downstream component…
CVE-2026-862958.3
A vulnerability was found in D-Link DIR-895L A1_102b07. This affects the function…

Frequently asked

Is CVE-2026-69097 being actively exploited?

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

How severe is CVE-2026-69097?

CVE-2026-69097 has a CVSS 3.1 base score of 7.0, rated high. EPSS estimates a 0.29% probability of exploitation.

Which products are affected by CVE-2026-69097?

Affected products include Gitpython Project Gitpython.

How do I fix CVE-2026-69097?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-69097 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

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