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.6%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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
Severity81% × 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.6%
EPSS %ILE
44th
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 28, 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(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-26/hub-rhel9:17896112742026-09-23redhat
redhatansible-automation-platform-25/hub-rhel8:17896063952026-09-23redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896370822026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896118582026-09-17redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17896076052026-09-17redhat
redhatsatellite/iop-vmaas-rhel9:17896119982026-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 31× in last 7d / 144× 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 239 total refreshes for this CVE.

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

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

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 on August 13, 2026, with the most recent update on September 28, 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.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73624?
CVE-2026-73624 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73624?
A fix for CVE-2026-73624 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73624 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-73624

Explore →

Is Your Infrastructure Affected by CVE-2026-73624?

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

Book a Demo →Browse All CVEs