CVE-2026-67623 in Mistral Vibe
Summary
by MITRE • 08/05/2026
Mistral Vibe before 2.23.3 contains a remote code execution vulnerability that allows attackers to execute arbitrary commands by embedding a malicious core.fsmonitor hook in a repository's .git/config file, which is triggered when vibe invokes git status --porcelain without suppressing hook execution. Attackers can distribute or create a crafted repository containing a malicious fsmonitor entry to achieve arbitrary command execution with the victim's full privileges when any vibe command is run inside that repository.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/05/2026
This vulnerability exists within Mistral Vibe versions prior to 2.23.3 and represents a critical remote code execution flaw that exploits the git repository management functionality. The vulnerability stems from improper handling of Git configuration files, specifically the core.fsmonitor hook mechanism, which allows attackers to inject malicious command sequences that execute with the privileges of the user running the vibe application.
The technical implementation of this exploit leverages Git's internal hook execution mechanisms through the .git/config file manipulation. When an attacker creates or distributes a repository containing a malicious fsmonitor entry within the configuration file, any invocation of vibe commands that internally call git status --porcelain without properly suppressing hook execution will trigger the embedded malicious code. This occurs because Git's status command processes hooks by default, and the core.fsmonitor configuration directive specifically enables hook execution for filesystem monitoring purposes.
The operational impact of this vulnerability is severe as it provides attackers with full system access equivalent to the victim user's privileges. Since vibe applications typically run with the same permissions as the user executing them, successful exploitation allows attackers to execute arbitrary commands including file manipulation, data exfiltration, privilege escalation, and persistence mechanism deployment. The vulnerability affects any environment where Mistral Vibe processes Git repositories, making it particularly dangerous in development environments, CI/CD pipelines, and collaborative coding platforms.
This vulnerability aligns with CWE-94, which describes "Improper Control of Generation of Code" and represents a code injection flaw that allows arbitrary command execution. The attack pattern follows the MITRE ATT&CK framework's T1059.007 technique for "Command and Scripting Interpreter: Python," as the malicious commands typically execute within Python-based Git operations. Additionally, this represents a privilege escalation vector through the exploitation of trust relationships in Git repository management systems.
The recommended mitigation strategy involves upgrading to Mistral Vibe version 2.23.3 or later, which implements proper sanitization of Git configuration file entries and disables automatic hook execution for status commands. Organizations should also implement repository scanning procedures to detect malicious fsmonitor configurations and establish secure coding practices for Git hook management. Network-level controls including outbound traffic filtering and repository access restrictions can provide additional defense-in-depth measures against this vulnerability class.