# CVE-2026-122133: Mistral Vibe before 2.25.5 on Windows Untrusted Search Path RCE via git.exe


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-4c2h-cpg4-cvr2

## What is CVE-2026-122133?

CVE-2026-122133 is a high-severity vulnerability in mistralai mistral-vibe, published on 4 Nov 2026. 

### Official 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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-122133?


## How do I fix CVE-2026-122133?

No fix has been published for CVE-2026-122133 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-122133 being exploited?

There is no known exploitation of CVE-2026-122133 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122133 and fix it if it is affected.

What it is: CVE-2026-122133 is a high-severity vulnerability in mistralai mistral-vibe, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122133 in the wild and no public exploit code.

Affected product: mistralai mistral-vibe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-122133/ (Markdown: https://insights.sbomify.com/CVE-2026-122133/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-122133
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-122133
- OSV: https://osv.dev/vulnerability/CVE-2026-122133

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-122133/
Summaries are generated and may contain mistakes; the official description above is the record.