CVE-2023-40267VulnerabilityPublished 11 Aug 2023Updated 3 Nov 2025

CVE-2023-40267: n/a

Source CVE Database V5

Mentioned vulnerabilities

CVE-2022-24439

Not known to be exploited · fixed in 3.1.32 : update affected systems when convenient.

Data as of 26 Oct 2026, 07:57 UTC

Severity

Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.1.32

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Aug 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Upgrade GitPython to version 3.1.32 or later, where this vulnerability has been fixed. No other mitigation or temporary workaround is indicated.

Description

GitPython versions before 3.1.32 contain a vulnerability where insecure non-multi options in the clone and clone_from functions are not properly blocked. This issue is a result of an incomplete fix for a previous vulnerability identified as CVE-2022-24439. The vulnerability was addressed in version 3.1.32.

Impact

The vulnerability allows insecure options to be used in GitPython's clone and clone_from functions, which may lead to unsafe operations when cloning repositories. No public exploit or in-the-wild exploitation is currently known. The impact is limited to the affected versions prior to 3.1.32.

Summary

GitPython prior to version 3.1.32 does not adequately block insecure non-multi options in its clone and clone_from methods. This vulnerability stems from an incomplete remediation of CVE-2022-24439. The flaw could potentially allow unsafe usage of these functions due to improper option handling. The issue was fixed in GitPython 3.1.32.

References

Community reviews

Loading reviews…