CVE-2026-67323

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-51805 (ENISA EUVD) · GHSA-4vpg-pfj8-m33q (GitHub Security Advisories) · GHSA-956x-8gvw-wg5v (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed

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.4HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
1.3%
EPSS %ILE
69th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 1, 2026

Last Modified

October 23, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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

Patch Availability(17)

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 rangeFix by version rangeDependents
python-git3.1.14-1 ... 3.1.50-1 (14 versions)
  • every version on: no fix on record
—
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 (103 versions)
  • every version up to 3.1.51: fixed in 3.1.51
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 333 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 233 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-67323?
CVE-2026-67323 is a high-severity vulnerability; its CVE record was 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.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…
When was CVE-2026-67323 made public?
CVE-2026-67323 was made public on July 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 1, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-67323 actively exploited?
CVE-2026-67323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67323?
CVE-2026-67323 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67323?
A fix for CVE-2026-67323 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67323 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-67323

Explore →

Is Your Infrastructure Affected by CVE-2026-67323?

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