# CVE-2026-93993: Mistral Vibe before 2.25.5 Remote Code Execution via git post-checkout

> Attackers can execute arbitrary shell commands by supplying a repository with a crafted git post-checkout hook that bypasses trust validation.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-92v2-hh9v-6vj5, openSUSE-SU-2026:11900-1

## What is CVE-2026-93993?

CVE-2026-93993 is a high-severity code injection vulnerability in mistralai mistral-vibe, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mistral-vibe` | openSUSE:Tumbleweed | All versions | 2.25.8-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-93993 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93993 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93993 is a high-severity code injection vulnerability in mistralai mistral-vibe, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93993 exists.

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-93993/ (Markdown: https://insights.sbomify.com/CVE-2026-93993/index.md)
```

## Sources

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

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