# CVE-2026-67623: Mistral Vibe < 2.23.3 Arbitrary Command Execution via git fsmonitor Hook

> Attackers can execute arbitrary commands with victim privileges by crafting a repository with a malicious git fsmonitor hook triggered by Mistral Vibe.

- **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:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-g6fr-w8c4-4935

## What is CVE-2026-67623?

CVE-2026-67623 is a high-severity command injection vulnerability in mistralai mistral-vibe, published on 5 Aug 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.23.3 contains a remote code execution vulnerability that allows attackers to execute arbitrary commands by embedding a malicious core.fsmonitor hook in a repository's .git/config file, which is triggered when vibe invokes git status --porcelain without suppressing hook execution. Attackers can distribute or create a crafted repository containing a malicious fsmonitor entry to achieve arbitrary command execution with the victim's full privileges when any vibe command is run inside that repository.

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

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


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

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

## Is CVE-2026-67623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67623 is a high-severity command injection vulnerability in mistralai mistral-vibe, published on 5 Aug 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: There is no known exploitation of CVE-2026-67623 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-67623/ (Markdown: https://insights.sbomify.com/CVE-2026-67623/index.md)
```

## Sources

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

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