CVE-2026-67324

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

GitPython 3.1.50 fails to recognize joined short-option forms such as -u (the short form of --upload-pack=) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clone_from(..., multi_options=..., allow_unsafe_options=False), an attacker can supply -u to bypass the gate that blocks --upload-pack/-u, causing Git to execute the specified helper command during clone. Fixed in 3.1.51.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 1, 2026

Last Modified

September 3, 2026

Advisory Details (2)

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

GitPython 3.1.50 Authentication Bypass via Joined Short Options | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-authentication-bypass-via-joined-short-options
github Patch Available🟡 PoC Available

GitPython unsafe clone option gate bypass through joined short options · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-v396-v7q4-x2qj

Vendor Advisories for CVE-2026-67324(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-tensorflow-cuda-py312-rhel9:17881860072026-09-08redhat
redhatpython3.12-gitpython-0:3.1.59-1.el9ap2026-08-24redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)——
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
gitpython3.1.503.1.51—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 39× in last 7d / 228× 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 397 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67324?
CVE-2026-67324 is a critical vulnerability published on August 1, 2026. GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of --upload-pack=<value>) when enforcing its default unsafe-option gate. When an application passes attacker-influenced clone options into Repo.clonefrom(..., multioptions=..., allowunsafeoptions=False),…
When was CVE-2026-67324 disclosed?
CVE-2026-67324 was first published in the National Vulnerability Database on August 1, 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-67324 actively exploited?
CVE-2026-67324 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 68.1% of all scored CVEs.
What is the CVSS score of CVE-2026-67324?
CVE-2026-67324 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-67324?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67324, 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-67324

Explore →

Is Your Infrastructure Affected by CVE-2026-67324?

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

Start Free Scan →Browse All CVEs