CVE-2026-67323

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.4EG
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.4Exploit: Elevated riskExposed: 0

A fix is available — apply it.

GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.ls_remote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.iter_commits() and Repo.blame() do not check for leading-dash revision arguments, so a revision like --output= can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.

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

Published

August 1, 2026

Last Modified

September 3, 2026

Advisory Details (2)

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

GitPython before 3.1.51 Command Injection via unguarded Git options | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitpython-before-command-injection-via-unguarded-git-options
github Patch Available🟡 PoC Available

command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file overwrite via `Repo.iter_commits()` / `Repo.blame()` · Advisory · gitpython-developers/GitPython · GitHub

https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-956x-8gvw-wg5v

Vendor Advisories for CVE-2026-67323(11)

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 / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17881858992026-09-08redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17881903822026-09-03redhat
redhatsatellite/iop-vmaas-rhel9:17882264992026-09-03redhat
redhatsatellite/iop-vmaas-rhel9:17882541612026-09-03redhat
redhatsatellite/iop-vulnerability-engine-rhel9:17881902242026-09-03redhat
redhatpython3.12-gitpython-0:3.1.59-1.el9ap2026-08-24redhat
redhatllvm21-main-21.1.8-8.hum12026-07-26redhat
redhatswift-lang-main-6.3.3-0.1.1.hum12026-07-25redhat
redhatllvm-main-22.1.8-4.1.hum12026-07-23redhat

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
gitpython0.1.7 ... 3.1.9 (103 versions)3.1.51—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 127× 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 244 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-67323?
CVE-2026-67323 is a high vulnerability published on August 1, 2026. GitPython before 3.1.51 fails to guard against dangerous Git options passed as keyword arguments in Repo.archive() and git.lsremote(), allowing command injection via options such as --exec/--upload-pack (leading to arbitrary command execution). Additionally, Repo.itercommits() and Repo.blame() do…
When was CVE-2026-67323 disclosed?
CVE-2026-67323 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-67323 actively exploited?
CVE-2026-67323 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 37.6% of all scored CVEs.
What is the CVSS score of CVE-2026-67323?
CVE-2026-67323 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-67323?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67323, 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-67323

Explore →

Is Your Infrastructure Affected by CVE-2026-67323?

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

Start Free Scan →Browse All CVEs