CVE-2026-122135 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
Mistral Vibe before 3.0.3 runs git log during project context collection, and a repository can set gpg.program so git executes an attacker's program. The program runs at session start, before any trust prompt, so an attacker gets command execution on the developer's machine.
first public Nov 4, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Developers who run Mistral Vibe on a repository they did not write or fully trust, because the project's git config is read at session start. Teams that only use Vibe on their own trusted repositories and keep the version current are less exposed. The sources do not say whether managed or hosted use is involved.
Not affected if trusted-repos-only, version-3.0.3-or-later
Who cares coding-agent, git, mistral-vibe
3.0.3gpg.program setting in .git/config, and log.showSignature enabled3.0.3 or laterMistral 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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.