Is CVE-2026-122134 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-122134 being exploited in the wild.

How severe is CVE-2026-122134?

High severity, with a CVSS score of 8.8, published 4 November 2026.

Is there a fix for CVE-2026-122134?

Yes: fixed in 2.25.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-122134 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-122134?

Check whether you run Mistral Vibe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-122134: Mistral Vibe remote code execution via malicious Git filters

CVE-2026-122134 · Severity: high · CVSS 8.8 · Published 2026-11-04

Mistral Vibe is a CLI coding agent that automatically analyzes and modifies code repositories. Attackers can create malicious repositories with specially configured Git clean or process filter drivers that execute arbitrary commands when a user opens the repository in Mistral Vibe, before any security prompt appears. This allows complete compromise of the user's system with their privileges.

Technologies: Mistral Vibe. Vendors: Mistral.

Quick answers

Is CVE-2026-122134 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122134 being exploited in the wild.
How severe is CVE-2026-122134?: High severity, with a CVSS score of 8.8, published 4 November 2026.
Which products and versions are affected?: Mistral Vibe before 2.25.7.
Is there a fix for CVE-2026-122134?: Yes: fixed in 2.25.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122134 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-122134?: Check whether you run Mistral Vibe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.25.7

Technical details

The vulnerability exists in ProjectContextProvider._fetch_git_status, which runs `git status` at application startup to check repository state. Malicious Git filters defined in the repository's configuration (clean or process filters) execute during this operation before any trust or safety prompt is presented to the user. The attacker gains code execution with the user's privileges; a fix is available in version 2.25.7 and later.

Affected products

Mistral Vibe before 2.25.7

Timeline

2026-11-04: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.