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

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

Affects mistral-vibeSource GCVE Database

Compare

Authoritative record:CVE-2026-78677· High 8.7

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

Data as of 30 Oct 2026, 07:44 UTC

CVSS 4.0 base score

8.7High

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

Patch: Available – fixed in 2.26.0

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
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 mistral-vibe to 2.26.0.

Affected software

Product	Affected	Fixed in
Homebrewmistral-vibe`pkg:brew/mistral-vibe`Other threats	Affected >=2.1.0 <2.26.0	Fixed in 2.26.0

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

AI-suggested

A patch is available in GitPython version 2.26.0 that adds --separate-git-dir to the unsafe_git_clone_options denylist, blocking its use unless allow_unsafe_options=True is explicitly set. Users should upgrade to version 2.26.0 or later to remediate this vulnerability. Until patched, avoid passing separate_git_dir or separate-git-dir options to Repo.clone_from() or Repo.clone(), or explicitly set allow_unsafe_options=True only if the input is fully trusted. No other mitigations are recommended as the issue is a logic flaw in option filtering.

Description

GitPython versions from 2.1.0 up to but not including 2.26.0 have a vulnerability where the clone_from() and clone() methods do not block the --separate-git-dir option by default, despite documentation stating they should. This allows an attacker controlling input to specify an arbitrary filesystem path for the Git metadata directory, leading to creation of repository metadata outside the intended clone destination. The flaw arises from an incomplete denylist of unsafe clone options, omitting --separate-git-dir, which is recognized as unsafe in other contexts within GitPython. The impact is arbitrary directory and file creation at attacker-controlled locations, bounded only by filesystem permissions of the running process. A fix is available in version 2.26.0.

Impact

An attacker able to control the separate_git_dir argument passed to Repo.clone_from() or Repo.clone() can cause GitPython to execute git clone with the --separate-git-dir option pointing to an arbitrary filesystem path. This results in creation of the full Git repository metadata tree (including hooks) at the attacker-controlled location outside the intended clone destination. The impact is arbitrary directory and file creation limited only by the filesystem permissions of the process running GitPython. This can lead to unauthorized file system modifications and potential security risks related to malicious Git hooks or repository metadata manipulation. The CVSS 3.1 score is 7.5 (High) with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact.

Summary

GitPython's Repo.clone_from() and Repo.clone() methods forward keyword arguments to the underlying git clone command, filtering unsafe options via a denylist (Repo.unsafe_git_clone_options). However, the --separate-git-dir option, which redirects the repository's .git metadata directory to an arbitrary path, is missing from this denylist. Although the documentation states that allow_unsafe_options=False (default) should block --separate-git-dir, it does not. This allows an attacker who can influence the separate_git_dir or separate-git-dir argument to cause git clone to create repository metadata at an arbitrary filesystem location outside the intended clone directory. This vulnerability is due to a parity gap between denylist entries for git init and git clone commands. The impact is arbitrary directory and file creation at attacker-controlled paths, potentially enabling malicious repository hooks or other artifacts. The vulnerability affects GitPython versions >=2.1.0 <2.26.0 and is fixed in 2.26.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 07:44 UTC

Technical details

References

Community reviews

Related threats