Mistral Vibe before 2.25.5 on Windows Untrusted Search Path RCE via git.exe
Mistral Vibe before 2.25.5 on Windows is affected when a malicious git.exe sits in a repository root that is opened. Fixed in 2.25.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.25.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Mistral Vibe before 2.25.5 on Windows A malicious git.exe is placed in the repository root The victim opens the crafted repository
- 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-122133 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.5.
- 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.5
- 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 on Windows contains an untrusted search path flaw that lets an attacker run code by placing a malicious git.exe in a repository root. The attacker can reach it remotely, without logging in, if a user is lured into opening a crafted repository, because the software runs that git.exe at session start before any trust prompt appears.
Read the original description
Mistral Vibe before 2.25.5 on Windows contains an untrusted search path vulnerability that allows attackers to execute code by placing git.exe in a repository root. Attackers can lure users into opening a crafted repository so SessionLogger and ProjectContextProvider run the malicious git.exe at session start before any trust prompt.
What to do
Check whether your setup matches what the bug needs.
Affects Mistral Vibe before 2.25.5 on Windows A malicious git.exe is placed in the repository root The victim opens the crafted repositoryUpgrade to a fixed version: 2.25.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- mistralai mistral-vibe
fixed in 2.25.5
Evidence 7
- Patch
- Repository
- Repository
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122133
Is CVE-2026-122133 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?
On Windows, Mistral Vibe can run a git.exe file found in the repository root instead of the trusted git program. An attacker who places a malicious git.exe there can execute code on the Windows system.Source: vulncheck.com
Which versions are affected by CVE-2026-122133?
mistral-vibe: before 2.25.5.Source: cve.now feed data
Am I affected, and how do I check?
The issue affects Mistral Vibe versions before 2.25.5 on Windows. To check a setup, confirm the installed Mistral Vibe version and whether it runs on Windows.Source: vulncheck.com
How do I fix CVE-2026-122133?
Upgrade Mistral Vibe to version 2.25.5 or later, which contains the fix. The sources provided do not list a workaround.Source: vulncheck.com