CVE-2026-73623

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: Elevated riskExposed 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/100CISA SSVC

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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.8%
EPSS %ILE
56th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 3, 2026

Advisory Details (2)

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

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 Patch Available🟡 PoC Available

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

Vendor Advisories for CVE-2026-73623(10)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-25/hub-rhel8:17896063952026-09-23redhat
redhatansible-automation-platform-26/hub-rhel9:17896112742026-09-23redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatansible-automation-platform-27/hub-rhel9:17889187082026-09-14redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
redhatpython3.12-gitpython-0:3.1.59-1.el9pc2026-09-03redhat

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 28× in last 7d / 135× 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.

Showing the most recent 100 of 230 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73623?
CVE-2026-73623 is a high vulnerability published on August 13, 2026. GitPython before 3.1.54 contains an incomplete denylist in unsafegitclone_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 disclosed?
CVE-2026-73623 was first published on August 13, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73623 actively exploited?
CVE-2026-73623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th 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.

Book a Demo →Browse All CVEs