Mistral Vibe before 2.25.7 Code Execution via Git Filter Drivers
Mistral Vibe before 2.25.7 is affected when it opens a crafted Git repository containing malicious clean or process filter drivers, because it runs git status at startup. Fixed in 2.25.7.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.25.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Mistral Vibe versions before 2.25.7 The victim opens a crafted repository containing malicious Git clean or process filter drivers Mistral Vibe runs git status at startup, which invokes the filters
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
CVE-2026-122134 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects mistral-vibe; fixed in 2.25.7.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.25.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Mistral Vibe, before the fixed release, can be made to run attacker-chosen commands with the user's privileges when the user opens a specially crafted Git repository, because Git filter drivers configured in the repository execute during a startup `git status` check before any trust prompt appears. The attack is reached remotely, without logging in, but it does require the user to open the malicious repository.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Mistral Vibe versions before 2.25.7 The victim opens a crafted repository containing malicious Git clean or process filter drivers Mistral Vibe runs git status at startup, which invokes the filtersUpgrade to a fixed version: 2.25.7.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- mistralai mistral-vibe
fixed in 2.25.7
Evidence 6
- Patch
- Repository
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122134
Is CVE-2026-122134 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets a malicious Git repository run attacker-chosen commands with the user's privileges. Mistral Vibe runs git status at startup, which invokes the repository's clean or process filter drivers.Source: vulncheck.com
Which versions are affected by CVE-2026-122134?
mistral-vibe: before 2.25.7.Source: cve.now feed data
Am I affected, and how do I check?
Mistral Vibe versions before 2.25.7 are in scope. The setup involves opening a crafted repository that contains malicious Git clean or process filter drivers. Compare your installed Mistral Vibe version with 2.25.7 to check where it falls.Source: vulncheck.com
How do I fix CVE-2026-122134?
Upgrade Mistral Vibe to 2.25.7, the listed fixed version. The facts do not list a workaround.Source: vulncheck.com