CVE-2026-67323

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. the CNA's CVSS baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 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(high)
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
61%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 14, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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.50-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-git3.1.44-1, 3.1.45-1, 3.1.46-1, 3.1.50-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 46× in last 7d / 119× 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 119 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 14, 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 39.4% of all scored CVEs.
What is the CVSS score of CVE-2026-67323?
CVE-2026-67323 has a CVSS v4.0 base score of 8.4 (CNA self-assessment; NVD's own analysis pending).
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