How severe is CVE-2023-40267?

CVE-2023-40267 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2023-40267 being actively exploited?

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

What products are affected by CVE-2023-40267?

CVE-2023-40267 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-40267?

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

When was CVE-2023-40267 published?

CVE-2023-40267 was published on 2023-08-11 and last updated on 2026-06-17.

CVE-2023-40267

CVE-2023-40267 is a critical-severity vulnerability in Gitpython Project Gitpython with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gitpython Project Gitpython
Published: 2023-08-11
Last modified: 2026-06-17

Description

GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from. NOTE: this issue exists because of an incomplete fix for CVE-2022-24439.

Frequently asked questions

What is CVE-2023-40267?: GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from. NOTE: this issue exists because of an incomplete fix for CVE-2022-24439.
How severe is CVE-2023-40267?: CVE-2023-40267 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-40267 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (67th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-40267?: CVE-2023-40267 affects Gitpython Project Gitpython. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-40267?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2023-40267 published?: CVE-2023-40267 was published on 2023-08-11 and last updated on 2026-06-17.

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-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…
CVE-2026-73625 — High (CVSS 8.8): GitPython versions before 3.1.54 contain a remote code execution vulnerability in the check_unsafe_options guard that…

All CVEs affecting Gitpython Project Gitpython →