CVE-2026-110859VulnerabilityPublished 29 Oct 2026

mistral-vibe · GitPython: arbitrary file read via attacker-controlled branch name in `Head.checkout()` (incomplete fix of

Affects mistral-vibeSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-110859· High 8.7

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

Data as of 30 Oct 2026, 08:14 UTC

CVSS 4.0 base score

8.7High

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

Patch: Available – fixed in 3.0.3

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 14 Oct 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 3.0.3.

Affected software

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

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 3.0.3 that fixes this vulnerability. Users should upgrade to version 3.0.3 or later to remediate the issue. Until patched, avoid cloning and checking out repositories from untrusted sources using vulnerable GitPython versions.

Description

GitPython versions up to 3.1.62 contain a vulnerability in the Head.checkout() method that allows an attacker to cause an arbitrary file read via a specially crafted branch name. The flaw arises because the branch name is passed as a positional argument to git checkout without proper sanitization or argument separation, enabling injection of git command options such as --pathspec-from-file. This can cause the contents of arbitrary files readable by the application process to be returned in exceptions. The issue is a regression or incomplete fix of prior advisories and affects all published releases up to 3.1.62. A fix is available in version 3.0.3.

Impact

An attacker who can cause the application to clone a repository they control can exploit this vulnerability to read arbitrary files on the system accessible to the application's process. This is achieved by naming the default branch of the malicious repository with a payload that injects git command options to read files such as /etc/passwd. No credentials or privileges are required, and the attack can be triggered simply by cloning and checking out the repository. The confidentiality of sensitive files is compromised, but integrity and availability are not affected.

Summary

The vulnerability in GitPython's Head.checkout() method occurs because it does not properly sanitize its positional branch name argument before passing it to the underlying git checkout command. While keyword arguments are guarded against unsafe git options, the positional branch name is not inspected and is passed directly, allowing an attacker-controlled branch name such as '--pathspec-from-file=/etc/passwd' to cause git to read and expose arbitrary files. This vulnerability affects all published GitPython releases up to 3.1.62 and was verified with git 2.55.0. It is a regression or incomplete fix of two prior advisories (CVE-2026-76217 and CVE-2026-78679) where similar issues were fixed for keyword arguments and other methods but not for Head.checkout's positional argument. The vulnerability has a CVSS 3.1 base score of 7.5 (High) with network attack vector, low complexity, no privileges required, and high confidentiality impact. The fix is included in GitPython version 3.0.3.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 08:14 UTC

Technical details

References

Community reviews

Related threats