Description
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.
Published: 2026-08-05
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A malicious core.fsmonitor entry can be embedded in a repository’s .git/config file, which Mistral Vibe executes when it runs "git status --porcelain". The hook runs with the same privileges as the user running the application, enabling arbitrary command execution that can affect the entire system. The weakness corresponds to CWE‑829, a privilege escalation via system command execution.

Affected Systems

The affected product is Mistral Vibe from Mistralai. Versions prior to 2.23.3 are vulnerable.

Risk and Exploitability

The CVSS score is 8.6, indicating high severity. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires the victim to run any vibe command within a repository that contains a crafted .git/config entry, typically delivered through a malicious repository or by an attacker who gains access to an existing repository. The attack vector is local system context when the application is invoked.

Generated by OpenCVE AI on August 5, 2026 at 14:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Mistral Vibe to version 2.23.3 or later.
  • If an upgrade is not immediately possible, remove any core.fsmonitor entries from the .git/config file in repositories before running vibe commands.
  • Set the core.fsmonitor configuration to an empty string or disable hook execution in git to prevent automatic triggering of the hook.

Generated by OpenCVE AI on August 5, 2026 at 14:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 07 Aug 2026 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Mistral
Mistral mistral-vibe
Vendors & Products Mistral
Mistral mistral-vibe

Thu, 06 Aug 2026 13:15:00 +0000

Type Values Removed Values Added
References

Wed, 05 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Wed, 05 Aug 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Mistral Vibe < 2.23.3 Arbitrary Command Execution via git fsmonitor Hook
Weaknesses CWE-829
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Subscriptions

Mistral Mistral-vibe
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-06T12:35:02.125Z

Reserved: 2026-07-29T21:07:39.204Z

Link: CVE-2026-67623

cve-icon Vulnrichment

Updated: 2026-08-05T14:28:03.161Z

cve-icon NVD

Status : Received

Published: 2026-08-05T14:17:10.047

Modified: 2026-08-06T13:18:22.287

Link: CVE-2026-67623

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T10:06:27Z

Weaknesses
  • CWE-829

    Inclusion of Functionality from Untrusted Control Sphere