CVE-2026-69097

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-03. the CNA's CVSS baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.0
EG Score
7.0(high)
EG Risk
48(Track*)
EG Risk 48/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 computed
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 3, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

GitPython before 3.1.53 Config Injection via Submodule Names | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-config-injection-via-submodule-names
github Patch Available🟡 PoC Available

GitPython: git-config section-name injection enables arbitrary config directives (core.sshCommand RCE) · Advisory · gitpython-developers/GitPython · GitHub

Affected: 3.1.50); the

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-3rp5-jjmw-4wv2

Vendor Advisories for CVE-2026-69097(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.30-1 ... 3.1.50-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1——
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (105 versions)3.1.53—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 78× 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.

  1. 2026-08-20 23:35 UTCEG score recompute
  2. 2026-08-20 23:34 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 11:07 UTCGHSA enrichment
  5. 2026-08-19 22:40 UTCEG score recompute
  6. 2026-08-19 22:40 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:12 UTCGHSA enrichment
  9. 2026-08-18 21:44 UTCEG score recompute
  10. 2026-08-18 21:44 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:40 UTCGHSA enrichment
  14. 2026-08-17 19:56 UTCEG score recompute
  15. 2026-08-17 19:56 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 07:28 UTCGHSA enrichment
  18. 2026-08-16 19:01 UTCEG score recompute
  19. 2026-08-16 19:01 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 06:33 UTCEG score recompute
  23. 2026-08-16 06:33 UTCGHSA enrichment
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 18:06 UTCGHSA enrichment
Show 53 more
  1. 2026-08-15 05:39 UTCEG score recompute
  2. 2026-08-15 05:39 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 17:11 UTCEG score recompute
  5. 2026-08-14 17:11 UTCGHSA enrichment
  6. 2026-08-14 13:35 UTCGHSA enrichment
  7. 2026-08-14 01:08 UTCEG score recompute
  8. 2026-08-14 01:08 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 12:40 UTCGHSA enrichment
  11. 2026-08-13 00:13 UTCEG score recompute
  12. 2026-08-13 00:13 UTCGHSA enrichment
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-12 11:46 UTCGHSA enrichment
  15. 2026-08-11 23:18 UTCEG score recompute
  16. 2026-08-11 23:18 UTCGHSA enrichment
  17. 2026-08-11 10:51 UTCEG score recompute
  18. 2026-08-11 10:51 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 22:24 UTCGHSA enrichment
  21. 2026-08-10 09:57 UTCGHSA enrichment
  22. 2026-08-09 21:30 UTCEG score recompute
  23. 2026-08-09 21:30 UTCGHSA enrichment
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-09 09:03 UTCGHSA enrichment
  26. 2026-08-08 20:36 UTCEG score recompute
  27. 2026-08-08 20:36 UTCGHSA enrichment
  28. 2026-08-08 16:37 UTCEPSS rescore
  29. 2026-08-08 08:08 UTCGHSA enrichment
  30. 2026-08-07 19:41 UTCEG score recompute
  31. 2026-08-07 19:41 UTCGHSA enrichment
  32. 2026-08-07 07:14 UTCGHSA enrichment
  33. 2026-08-06 18:47 UTCEG score recompute
  34. 2026-08-06 18:47 UTCGHSA enrichment
  35. 2026-08-06 13:47 UTCEPSS rescore
  36. 2026-08-06 06:20 UTCEG score recompute
  37. 2026-08-06 06:20 UTCGHSA enrichment
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-05 17:53 UTCGHSA enrichment
  41. 2026-08-05 05:26 UTCEG score recompute
  42. 2026-08-05 05:26 UTCGHSA enrichment
  43. 2026-08-05 04:39 UTCEG score recompute
  44. 2026-08-05 04:39 UTCGHSA enrichment
  45. 2026-08-04 16:29 UTCEG score recompute
  46. 2026-08-04 16:29 UTCGHSA enrichment
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 04:02 UTCGHSA enrichment
  49. 2026-08-03 15:34 UTCEG score recompute
  50. 2026-08-03 15:34 UTCGHSA enrichment
  51. 2026-08-03 14:32 UTCEG score recompute
  52. 2026-08-03 13:34 UTCEG score recompute
  53. 2026-08-03 13:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69097?
CVE-2026-69097 is a high vulnerability published on August 3, 2026. 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…
When was CVE-2026-69097 disclosed?
CVE-2026-69097 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69097 actively exploited?
CVE-2026-69097 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 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-69097?
CVE-2026-69097 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69097, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69097

Explore →

Is Your Infrastructure Affected by CVE-2026-69097?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs