# CVE-2026-87984: Path traversal in mistral-vibe

> Attackers can write arbitrary files outside the workspace by exploiting missing permission checks on shell redirections in Mistral Vibe.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-4vx3-rfqx-v945

## What is CVE-2026-87984?

CVE-2026-87984 is a critical path traversal vulnerability in mistralai mistral-vibe, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file write vulnerability in Mistral Vibe, introduced in version 1.3.4, allows an attacker to create or overwrite files outside the active workspace without user approval. Shell redirection destinations are omitted from permission checks, enabling otherwise allowlisted commands to write to arbitrary paths accessible to the Vibe process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Apply the vendor's patch.

## Is CVE-2026-87984 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87984 is a critical path traversal vulnerability in mistralai mistral-vibe, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-87984 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-87984/ (Markdown: https://insights.sbomify.com/CVE-2026-87984/index.md)
```

## Sources

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

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