CVE-2026-73624

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.1; sources differ by 0.0.

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

A fix is available — apply it.

GitPython versions before 3.1.54 contain an arbitrary file overwrite vulnerability in the Diffable.diff method that fails to validate git options passed through kwargs. Attackers can supply the --output argument via the other parameter or output kwarg to write patch content to attacker-chosen file paths at process privilege level.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

GitPython before 3.1.54 Arbitrary File Overwrite via diff | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-arbitrary-file-overwrite-via-diff
github Patch Available🟡 PoC Available

Arbitrary file overwrite via git diff --output argument injection in Diffable.diff (key- and value-controlled) · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-fjr4-x663-mwxc

Vendor Advisories for CVE-2026-73624(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
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 rangeFixed inDependents
python-git3.1.30-1 ... 3.1.61-1 (11 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1, 3.1.61-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-13.1.61-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
gitpython0.1.7 ... 3.1.9 (106 versions)3.1.54—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 134× 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 171 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73624?
CVE-2026-73624 is a high vulnerability published on August 13, 2026. GitPython versions before 3.1.54 contain an arbitrary file overwrite vulnerability in the Diffable.diff method that fails to validate git options passed through kwargs. Attackers can supply the --output argument via the other parameter or output kwarg to write patch content to attacker-chosen file…
When was CVE-2026-73624 disclosed?
CVE-2026-73624 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73624 actively exploited?
CVE-2026-73624 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 73.1% of all scored CVEs.
What is the CVSS score of CVE-2026-73624?
CVE-2026-73624 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-73624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73624, 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-73624

Explore →

Is Your Infrastructure Affected by CVE-2026-73624?

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

Start Free Scan →Browse All CVEs