How severe is CVE-2026-67323?

CVE-2026-67323 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-67323 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-67323?

CVE-2026-67323 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-67323?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-67323 published?

CVE-2026-67323 was published on 2026-08-01 and last updated on 2026-09-03.

CVE-2026-67323

CVE-2026-67323 is a high-severity vulnerability in Gitpython Project Gitpython with a CVSS 3.x base score of 8.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-77.

Key facts

Severity: High (CVSS 3.x base score 8.4)
CVSS v4: 8.6
EPSS exploit prediction: 1% (69th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-77
Affected product: Gitpython Project Gitpython
Published: 2026-08-01
Last modified: 2026-09-03

Description

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=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.

Frequently asked questions

What is CVE-2026-67323?: 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=<path> can cause Git to open and truncate an arbitrary file. Exploitation requires an application that passes attacker-controlled arguments to these methods.
How severe is CVE-2026-67323?: CVE-2026-67323 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-67323 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-67323?: CVE-2026-67323 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-67323?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-67323 published?: CVE-2026-67323 was published on 2026-08-01 and last updated on 2026-09-03.

References

Affected products (1)

cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*

More vulnerabilities in Gitpython Project Gitpython

CVE-2026-78676 — Critical (CVSS 9.8): GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting…
CVE-2026-67324 — Critical (CVSS 9.8): GitPython 3.1.50 fails to recognize joined short-option forms such as -u<value> (the short form of…
CVE-2023-40267 — Critical (CVSS 9.8): GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from. NOTE: this issue exists…
CVE-2026-87817 — High (CVSS 8.8): GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the…
CVE-2026-76221 — High (CVSS 8.8): GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows…
CVE-2026-76220 — High (CVSS 8.8): GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be…

All CVEs affecting Gitpython Project Gitpython →

Other CWE-77 (Command Injection) vulnerabilities

CVE-2026-105484 — Critical (CVSS 10.0): A security vulnerability has been detected in TOTOLINK X6000R 9.4.0cu.652_B20230116. The impacted element is the…
CVE-2026-105134 — Critical (CVSS 10.0): A flaw has been found in Ahsay AhsayCBS up to 10.3.2. This vulnerability affects unknown code of the file…
CVE-2026-102240 — Critical (CVSS 10.0): A vulnerability was found in Netcore NAP930 0.1.241010.141410. This affects the function eval of the file…
CVE-2026-101076 — Critical (CVSS 10.0): A vulnerability was detected in Netcore NR289-GE 1.4.5102. This affects the function system of the file…
CVE-2026-101075 — Critical (CVSS 10.0): A security vulnerability has been detected in Netcore NR289-GE 1.4.5102. The impacted element is the function system of…
CVE-2026-101072 — Critical (CVSS 10.0): A vulnerability was identified in Netcore NR289-GE 1.4.5102. This issue affects the function system of the file…

Browse all CWE-77 (Command Injection) vulnerabilities →