CVE-2026-69097

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.3 under NVD CVSS. EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-24) is not newer than that change (2026-10-23), so it does not.

Triggered by: Headline CVSS from NVD CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS
Elevated

Also known asEUVD-2026-52290 (ENISA EUVD) · GHSA-3rp5-jjmw-4wv2 (GitHub Security Advisories) · GHSA-9xx9-hw38-h2w9 (GitHub Security Advisories) · PYSEC-2026-3981 (OSV.dev)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 3, 2026

Last Modified

October 23, 2026

Advisory Details (2)

Auto-updated Aug 3, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17927211922026-10-29redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17925631272026-10-21redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918163162026-10-21redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17915561282026-10-19redhat
pipgitpython @ 3.1.53 (fixes <= 3.1.52)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.30-1, 3.1.30-1+deb12u2
  • every version up to 3.1.30-1+deb12u3: fixed in 3.1.30-1+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1
  • every version up to 3.1.44-1+deb13u1: fixed in 3.1.44-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1
  • every version up to 3.1.61-1: fixed in 3.1.61-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
gitpython0.1.7 ... 3.1.9 (105 versions)
  • every version up to 3.1.53: fixed in 3.1.53
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 275 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 175 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-11-11 02:03 UTCEchelonGraph re-scored
  4. 2026-11-11 02:03 UTCVendor advisory
  5. 2026-11-11 02:03 UTCGHSA enrichmentGHSA-3rp5-jjmw-4wv2 · GitHub severity HIGH · GitHub CVSS 7.0
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-11-03 23:41 UTCEchelonGraph re-scored
  14. 2026-11-03 23:41 UTCVendor advisory
  15. 2026-11-03 23:41 UTCGHSA enrichmentGHSA-3rp5-jjmw-4wv2 · GitHub severity HIGH · GitHub CVSS 7.0
  16. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-3rp5-jjmw-4wv2 · GitHub severity HIGH · GitHub CVSS 7.0
  20. 2026-11-01 07:40 UTCEchelonGraph re-scored
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-27 21:07 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-10-25 14:09 UTCEchelonGraph re-scored
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-23 21:29 UTCEchelonGraph re-scored
  7. 2026-10-23 21:29 UTCVendor advisory
  8. 2026-10-23 21:29 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-20 18:37 UTCEchelonGraph re-scored
  13. 2026-10-20 18:37 UTCVendor advisory
  14. 2026-10-20 18:37 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-18 03:19 UTCEchelonGraph re-scored
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-10-13 09:58 UTCEchelonGraph re-scored
  25. 2026-10-13 09:58 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  26. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-10-12 15:44 UTCEchelonGraph re-scored
  28. 2026-10-11 19:29 UTCEchelonGraph re-scored
  29. 2026-10-11 16:45 UTCEchelonGraph re-scored
  30. 2026-10-11 14:05 UTCEchelonGraph re-scored
  31. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-10-06 23:46 UTCEchelonGraph re-scored
  37. 2026-10-06 23:46 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  38. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-10-05 19:48 UTCEchelonGraph re-scored
  40. 2026-10-05 19:48 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  41. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-10-04 23:45 UTCEchelonGraph re-scored
  43. 2026-10-04 23:45 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  44. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-10-04 06:19 UTCEchelonGraph re-scored
  46. 2026-10-04 06:19 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  47. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-10-03 02:16 UTCEchelonGraph re-scored
  49. 2026-10-03 02:16 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  50. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-10-02 10:21 UTCEchelonGraph re-scored
  52. 2026-10-02 10:21 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  53. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-10-01 15:00 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  55. 2026-10-01 02:33 UTCEchelonGraph re-scored
  56. 2026-10-01 02:33 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  57. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-09-29 06:41 UTCEchelonGraph re-scored
  59. 2026-09-29 06:41 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  60. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-09-28 07:07 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  62. 2026-09-27 18:15 UTCEchelonGraph re-scored
  63. 2026-09-27 18:15 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  64. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  65. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  66. 2026-09-25 04:47 UTCEchelonGraph re-scored
  67. 2026-09-25 04:47 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  68. 2026-09-24 10:52 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  69. 2026-09-23 22:21 UTCEchelonGraph re-scored
  70. 2026-09-23 22:21 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  71. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-09-23 09:54 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  73. 2026-09-22 21:26 UTCEchelonGraph re-scored
  74. 2026-09-22 21:26 UTCGHSA enrichmentGHSA-9xx9-hw38-h2w9 · GitHub severity HIGH · GitHub CVSS 7.0
  75. 2026-09-22 05:29 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-69097?
CVE-2026-69097 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-69097 was made public on July 20, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 3, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-69097 actively exploited?
CVE-2026-69097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69097?
CVE-2026-69097 has a CVSS base score of 7.3 (NVD).
How do I remediate CVE-2026-69097?
A fix for CVE-2026-69097 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69097 are linked in the Vendor Advisories panel on this page.

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.