CVE-2026-73623

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (61st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 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-08-13) is not newer than that change (2026-10-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-57792 (ENISA EUVD) · GHSA-2726-phmx-rc26 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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: 1.0%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GitPython before 3.1.54 contains an incomplete denylist in unsafe_git_clone_options that omits --template, allowing attackers to achieve arbitrary command execution during clone operations. Attackers can supply --template pointing to a directory containing malicious post-checkout hooks that execute when git clones the repository.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 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
1.0%
EPSS %ILE
61st
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS. 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 13, 2026

Last Modified

October 24, 2026

Advisory Details (2)

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

GitPython before 3.1.54 Remote Code Execution via --template | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-remote-code-execution-via-template
GitHub advisoryMentions a patch (unverified)

Incomplete unsafe_git_clone_options denylist omits --template enabling arbitrary command execution via clone hooks · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-6p8h-3wgx-97gf

Patch Availability(12)

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.30-1 ... 3.1.62-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-git3.1.44-1 ... 3.1.62-2 (7 versions)
  • every version on: no fix on record
—
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 (106 versions)
  • every version up to 3.1.54: fixed in 3.1.54
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 66× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 288 refreshes 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 188 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73623?
CVE-2026-73623 is a high-severity vulnerability; its CVE record was published on August 13, 2026. GitPython before 3.1.54 contains an incomplete denylist in unsafe_git_clone_options that omits --template, allowing attackers to achieve arbitrary command execution during clone operations. Attackers can supply --template pointing to a directory containing malicious post-checkout hooks that execute…
When was CVE-2026-73623 made public?
CVE-2026-73623 was made public on July 22, 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 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73623 actively exploited?
CVE-2026-73623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73623?
CVE-2026-73623 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-73623?
A fix for CVE-2026-73623 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73623 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-73623

Explore →

Is Your Infrastructure Affected by CVE-2026-73623?

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