Quick answers
- Is CVE-2026-122135 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122135 being exploited in the wild.
- How severe is CVE-2026-122135?
- High severity, with a CVSS score of 8.8, published 4 November 2026.
- Which products and versions are affected?
- Mistral Vibe before 3.0.3.
- Is there a fix for CVE-2026-122135?
- Yes: fixed in 3.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-122135 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-122135?
- 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: 3.0.3
Technical details
The vulnerability exists in Mistral Vibe's project context collection, which runs Git commands including `git log` with configuration settings loaded from the repository. An attacker can set the `gpg.program` and `log.showSignature` Git configuration options in a malicious repository to cause Git to execute an arbitrary program during context startup, before any user interaction or trust prompt. The attack requires the victim to open a repository they do not fully control or trust.
Affected products
- Mistral Vibe before 3.0.3
Timeline
- 2026-11-04: disclosed