CVE-2026-122133mistralai mistral-vibe uncontrolled search path
CVE-2026-122133 is a uncontrolled search path in mistralai mistral-vibe, rated high (8.6 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
The software loads libraries or programs from a location an attacker can write to.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run their code inside your build or your running service.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.37% chance of exploitation activity in the next 30 days, higher than 32% of scored CVEs.
What to do
- Upgrade mistralai mistral-vibe to 2.25.5 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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 this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
- Update channels. The flaw sits between third-party code and your build or runtime.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.
Questions to answer about your own systems
- Where does mistralai mistral-vibe run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Releases
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.