CVE-2026-78677VulnerabilityPublished 4 Sep 2026Updated 26 Oct 2026

cruft · GitPython: clone_from()/clone() omit --separate-git-dir from unsafe_git_clone_options, enabling arbitrary

Affects cruftSource GCVE Database

Authoritative record:CVE-2026-78677· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2.16.0_15 soon.

Data as of 26 Oct 2026, 17:41 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Aug 2026
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Upgrade cruft to 2.16.0_15.

Affected software

Product	Affected	Fixed in
Homebrewcruft`pkg:brew/cruft`Other threats	Affected >=2.9.0 <2.16.0_15	Fixed in 2.16.0_15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in GitPython version 2.16.0_15, which adds --separate-git-dir to the unsafe_git_clone_options denylist, preventing its use unless allow_unsafe_options=True is explicitly set. Users should upgrade to version 2.16.0_15 or later. Until upgraded, applications should avoid forwarding the separate_git_dir or separate-git-dir option to Repo.clone_from() or Repo.clone(), or explicitly set allow_unsafe_options=True only if they fully trust the input. No other mitigations are documented.

Description

GitPython versions from 2.9.0 up to 2.16.0_15 have a vulnerability where the clone_from() and clone() methods omit the --separate-git-dir option from their unsafe options denylist. This omission allows an attacker to specify an arbitrary path for the Git repository metadata directory, enabling creation of repository files and directories outside the intended clone destination. The flaw arises from a denylist parity gap between clone and init commands, despite documentation stating that --separate-git-dir should be blocked by default. This can lead to arbitrary directory creation controlled by the attacker within the filesystem permissions of the process running GitPython.

Impact

An attacker able to influence the separate_git_dir argument to Repo.clone_from() or Repo.clone() can cause GitPython to create a full Git repository metadata structure at an arbitrary filesystem location outside the intended clone destination. This includes directories like hooks/, objects/, refs/, and files such as config and HEAD. This can lead to arbitrary directory and file creation with attacker-controlled content, potentially enabling further attacks such as planting malicious Git hooks or manipulating repository metadata. The impact is high confidentiality impact (arbitrary file creation) but no direct integrity or availability impact is described. The vulnerability is bounded by the filesystem permissions of the process running GitPython.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 17:41 UTC

Technical details

References

Community reviews

Related threats