Coding agents that inspect a repository on open are one bad .git/config away from running attacker code. On November 4, 2026, VulnCheck published three High-severity CVEs against Mistral Vibe that do exactly that—and they run before the trust prompt that is supposed to gate untrusted projects.
The three paths
All three share a timing failure: Vibe reads Git state at session start, and whatever the repository’s own Git configuration points at executes with the user’s privileges first.
CVE-2026-122133 (CWE-427, Windows only). Before 2.25.5, Vibe could pick up a git.exe planted in the repository root via an untrusted search path. Session startup code ran that binary before any trust UI. Fixed in v2.25.5 (September 18, 2026).
CVE-2026-122134 (CWE-829). Before 2.25.7, opening a crafted repo let malicious Git clean or process filter drivers fire when ProjectContextProvider._fetch_git_status ran git status. No Windows required. A repository extracted from an archive can carry its own .git/config; a plain git clone does not copy the sender’s config. Fixed in v2.25.7 (September 22, 2026). VulnCheck scores it CVSS 4.0 8.6 / CVSS 3.1 8.8.
CVE-2026-122135 (CWE-829). Before 3.0.3, a repo that sets gpg.program and log.showSignature on a signed commit made git log run the attacker’s program during project-context collection. Fixed in v3.0.3 (October 26, 2026).
Credit on all three goes to Francisco Rosales of Manifold Security. There are no public reports of in-the-wild exploitation as of the disclosure write-ups.
The version trap
It is easy to read “fixed in 2.25.7” and stop. That is wrong for this batch. v2.25.8 (last 2.25) and v2.26.1 (last 2.26) still call git log without --no-show-signature, so CVE-2026-122135 survives on both lines through 3.0.2. The safe floor for all three is 3.0.3 or later; 3.1.0 is the current release called out in incident tracking.
Mistral’s own advisory index still features MAI-2026-003 (September 14, 2026) for earlier Vibe shell-permission issues and does not yet list a dedicated advisory for these three Git-config CVEs. The durable public records are VulnCheck, NVD (Received), and the GitHub Advisory Database entries published minutes after the CVEs.
What to do
- Run
vibe --version. Anything below 3.0.3 leaves at least one of the three open—move to 3.0.3+. - Before opening a repo you did not write, inspect
.git/configforgpg.program,log.showSignature,filter/clean/processentries, and on Windows check the root for a plantedgit.exe. - Prefer a fresh clone over opening a downloaded archive in place, and keep approval prompts on while you survey unfamiliar projects.
The pattern for every coding agent
Any tool that auto-runs git status, git log, or a project-local Git binary before a trust gate inherits this class of bug. If you build or configure coding agents, treat repository-local Git configuration as untrusted input until the user has explicitly approved the workspace—and pin your agent CLI past the fixed floor, not merely “a recent 2.x.”