CVE-2026-122135 Mistral Vibe before 3.0.3 RCE via Repository-Configured gpg.program
High 8.6
Published
Updated
Check this codebase for CVE-2026-122135 and fix it if it is affected.
What it is: CVE-2026-122135 is a high-severity vulnerability in mistralai mistral-vibe, published on 4 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-122135 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-122135/ (Markdown: https://insights.sbomify.com/CVE-2026-122135/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-122135?
CVE-2026-122135 is a high-severity vulnerability in mistralai mistral-vibe, published on 4 Nov 2026.
Official description
Mistral Vibe before 3.0.3 contains a remote code execution vulnerability that allows attackers to run commands by abusing repository-configured gpg.program during project context collection. A crafted repository setting gpg.program and log.showSignature with a signed commit makes git log execute the attacker's program at session start, before any trust prompt.
Weakness: CWE-829
Which versions are affected by CVE-2026-122135?
How do I fix CVE-2026-122135?
No fix has been published for CVE-2026-122135 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-122135 being exploited?
There is no known exploitation of CVE-2026-122135 in the wild and no public exploit code.
Sources
Also known as GHSA-qx7j-gch3-gv7c.