CVE-2026-73625

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that can be bypassed by smuggling git options inside single-character kwarg values. Attackers can supply crafted option dictionaries to clone_from, fetch, pull, push, ls_remote, iter_commits, blame, or archive methods to execute arbitrary OS commands via the --upload-pack parameter.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

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 kwarg value smuggling | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-remote-code-execution-via-kwarg-value-smuggling
github Patch Available🟡 PoC Available

Unsafe git option guard bypass via single-character kwarg value token smuggling enables arbitrary command execution · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-r9mr-m37c-5fr3

Vendor Advisories for CVE-2026-73625(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 37× in last 7d / 131× 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 167 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73625?
CVE-2026-73625 is a high vulnerability published on August 13, 2026. GitPython versions before 3.1.54 contain a remote code execution vulnerability in the checkunsafeoptions guard that can be bypassed by smuggling git options inside single-character kwarg values. Attackers can supply crafted option dictionaries to clonefrom, fetch, pull, push, lsremote,…
When was CVE-2026-73625 disclosed?
CVE-2026-73625 was first published in the National Vulnerability Database 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-73625 actively exploited?
CVE-2026-73625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.2% of all scored CVEs.
What is the CVSS score of CVE-2026-73625?
CVE-2026-73625 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-73625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73625, 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-73625

Explore →

Is Your Infrastructure Affected by CVE-2026-73625?

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

Start Free Scan →Browse All CVEs