CVE Alert: CVE-2026-122134 – mistralai – mistral

Mistral Vibe before 2.25.7 contains a remote code execution vulnerability that allows attackers to run commands by configuring malicious Git clean or process filter drivers in a repository. When a user opens a crafted repository, ProjectContextProvider._fetch_git_status runs git status at startup, invoking the filters and executing commands with user privileges before any trust prompt.

**Risk verdict:** High risk for developer workstations; promptly patch because opening an untrusted repository can trigger code execution without a trust prompt.

**Why this matters:** Successful execution inherits the user’s permissions, potentially exposing source code, credentials, local configuration and access tokens, or enabling tampering with code and build outputs. KEV, SSVC, PoC and EPSS data were not provided, so active exploitation and wider campaign urgency cannot be assessed.

**Most likely attack path:** An attacker supplies a crafted repository through a pull request, archive, clone or shared workspace; the victim opens it in the application. Network delivery is feasible, complexity and attacker privileges are low, but active user interaction is required. Scope is unchanged, so direct cross-boundary impact is not indicated; however, access available to the user may expose connected development systems.

**Who is most exposed:** Developers and automation operators using the tool to inspect repositories from external contributors, public projects or other untrusted sources. Workstations with broad repository, cloud or CI credentials carry greater business risk.

Review process-creation telemetry for unexpected child processes when the application opens a repository.

Inspect repository Git configuration for clean or process filter-driver settings.

Check endpoint and shell logs for unusual commands or outbound connections after repository opening.

Mitigation and prioritisation

Upgrade promptly to the vendor-fixed release; confirm the installed package is no longer affected.

Until patched, avoid opening untrusted repositories and disable or restrict automatic repository inspection where feasible.

Use least-privilege accounts and isolate development environments from production credentials.

Coordinate rollout with developers, then validate on a test workstation before broad deployment.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.