CVE-2026-122133 in Mistral Vibe
Summary
by MITRE • 11/04/2026
Mistral Vibe before 2.25.5 on Windows contains an untrusted search path vulnerability that allows attackers to execute code by placing git.exe in a repository root. Attackers can lure users into opening a crafted repository so SessionLogger and ProjectContextProvider run the malicious git.exe at session start before any trust prompt.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/04/2026
The vulnerability identified in Mistral Vibe prior to version 2.25.5 represents a classic untrusted search path flaw, specifically categorized under CWE-427 which involves an application searching for executable files in directories that are not fully controlled by the software vendor or trusted sources. This architectural weakness allows attackers to manipulate the execution flow of legitimate system utilities by exploiting how the operating system resolves command names when no explicit file extension is provided during a process invocation. In this specific context, the vulnerability centers on the application's interaction with Git, a widely used version control system. When Mistral Vibe initiates operations that require access to repository metadata or history, it invokes git.exe without specifying its absolute path. Consequently, the Windows operating system searches for the executable in a series of directories defined by the PATH environment variable and potentially other local search paths associated with the current working directory or project root.
The operational impact of this flaw is significant because it enables arbitrary code execution through social engineering tactics rather than requiring direct exploitation of complex memory corruption bugs. An attacker can craft a malicious repository structure that includes a file named git.exe, which contains payload logic designed to compromise the host system. By luring a victim into opening or cloning this crafted repository within Mistral Vibe, the application inadvertently triggers the execution of the malicious binary during its initialization sequence. Specifically, components such as SessionLogger and ProjectContextProvider are responsible for setting up the user session and loading project context data upon startup. These modules execute commands related to Git operations before any security prompts or trust verification mechanisms can intervene. This timing is critical because it allows the attacker's code to run with the same privileges as the victim, effectively bypassing standard user consent dialogs that might otherwise block unauthorized installations or modifications.
From a threat intelligence perspective, this vulnerability aligns with MITRE ATT&CK technique T1204.002, which describes User Execution via Malicious File associated with Lures and Phishing. The attack vector relies heavily on the victim's action of opening a file or repository that appears legitimate but contains embedded malicious artifacts. Once executed, the payload can perform various hostile actions depending on its design, ranging from data exfiltration to establishing persistent backdoors within the system environment. Because the execution occurs at session start, it may also evade certain endpoint detection systems that monitor for suspicious activity only after initial user interaction or during active application usage phases rather than startup sequences.
Mitigation strategies must focus on eliminating the untrusted search path condition and enforcing strict binary signing verification. The primary remediation is to upgrade Mistral Vibe to version 2.25.5 or later, where developers have presumably implemented absolute paths for invoking system utilities like git.exe, thereby removing ambiguity in file resolution. Additionally, organizations should enforce application control policies such as Microsoft AppLocker or Windows Defender Application Control to restrict the execution of executables from writable directories unless they are digitally signed by a trusted publisher. Security awareness training is also essential to educate users about the risks of opening repositories or files from untrusted sources, particularly those that may contain unexpected executable binaries disguised as standard tools like git.exe. Regular auditing of PATH variables and ensuring that user-writable directories do not take precedence in search paths can further reduce the attack surface for similar vulnerabilities across other applications.