High priorityDisclosed

Advisory · CVE-2026-122134

Mistral Vibe runs malicious Git filter drivers before any trust prompt

Mistral Vibe before 2.25.7 contains a remote code execution flaw: a crafted repository can configure malicious Git clean or process filter drivers that run when the tool checks Git status at startup, before any trust prompt. Rated high at CVSS 3.1 8.8.

Advisory published November 4, 2026Independent summary
Vendor
Mistral AI
Product
Mistral Vibe
Identifier / CWE
CVE-2026-122134
CWE-829
Action timing
Immediate
ELI5

Explain it like I’m five

A project can carry its own instructions for helper programs that Git should run. The coding agent checks the project status before asking whether it is trusted, and Git obediently runs the project's helpers, giving the attacker code execution.

SIMPLIFIED_ATTACK_PATH04 STEPS
  1. 01Crafted repository

    An attacker prepares a repository configuring malicious Git clean or process filter drivers and gets a user to open it.

  2. 02Startup status check

    Mistral Vibe runs Git status during project context collection at session start.

  3. 03Filter invoked before trust prompt

    Git invokes the repository-configured filter drivers before any trust prompt is shown.

  4. 04Code execution

    The filter commands execute with the user's privileges.

What happened

Mistral Vibe before 2.25.7 contains a remote code execution vulnerability. Attackers can run commands by configuring malicious Git clean or process filter drivers in a repository. When a user opens a crafted repository, the tool’s project context collection runs Git status at startup, invoking the filters and executing commands with user privileges before any trust prompt. The issue is rated high at CVSS 3.1 8.8.

The fix is in Mistral Vibe 2.25.7; earlier versions are affected.

What to do

  1. Check the Mistral Vibe version on developer workstations and upgrade to 2.25.7 or later.
  2. Avoid opening repositories from untrusted sources until upgraded.
  3. Inspect repository Git configuration for unexpected clean or process filter driver definitions before opening unfamiliar projects.
  4. If a malicious filter is found, treat the workstation as compromised: investigate what the filter ran and rotate credentials used on that machine.
  5. Confirm the deployed version after updating.

Management note

This is the second of three Mistral Vibe flaws disclosed the same day with the same root pattern: repository-controlled configuration executing before the trust decision. Developers routinely clone and open unfamiliar repositories, so the exposure is the everyday workflow itself. Upgrade past all three fixes.