Skip to content
High-Risk Remote Code Execution Vulnerability in Mistral Vibe

High-Risk Remote Code Execution Vulnerability in Mistral Vibe

First seen 5 Nov 2026, 02:49 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 5, 2026 at 02:50 UTC
  • •CVE-2026-122134 allows remote code execution in Mistral Vibe before version 2.25.7.
  • •Developers using untrusted repositories are particularly vulnerable to exploitation.
  • •Immediate patching is recommended to mitigate risks associated with this vulnerability.

Mistral Vibe versions before 2.25.7 contain a remote code execution vulnerability (CVE-2026-122134) that allows attackers to execute commands via malicious Git clean or process filter drivers in a repository. When a crafted repository is opened, the application runs git status at startup, executing commands with user privileges before any trust prompt. Developers and automation operators inspecting untrusted repositories are most at risk, as successful exploitation can expose sensitive data and allow code tampering. The vulnerability has a CVSS score of 8.6, indicating high severity. Users are advised to promptly upgrade to the fixed version and avoid opening untrusted repositories until patched. The vulnerability was disclosed on November 4, 2026, and is currently not reported as.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-04
CVE-2026-122134 published
Mistral Vibe vulnerability disclosed, allowing remote code execution through crafted Git repositories.
Sploitus
2026-11-05
CVE-2026-122134 advisory released
Redpacketsecurity issues a high-risk alert regarding the vulnerability, urging users to patch promptly.
Redpacketsecurity

More articles in this cluster (4)

Following this threat?

Track CVE-2026-122134 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of Mistral Vibe are affected?
Mistral Vibe versions prior to 2.25.7 are affected by this vulnerability.
What should I do if I can't patch immediately?
Avoid opening untrusted repositories and disable automatic repository inspection until you can apply the patch.
Is there any active exploitation reported?
Currently, there are no reports of active exploitation for this vulnerability.