CVE-2026-122135: Automatic git log / repository-configured gpg.program during project context
Before 3.0.3, Vibe collected project context with git log in a way that honored repository-configured gpg.program when log.showSignature was set, executing attacker code before the trust prompt. Intermediate 2.25.x/2.26.x floors do not include this fix.
Executive Summary & Technical Impact
Before 3.0.3, Vibe collected project context with git log in a way that honored repository-configured gpg.program when log.showSignature was set, executing attacker code before the trust prompt. Intermediate 2.25.x/2.26.x floors do not include this fix.
Tracked under CVE-2026-122135 (CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)), this vulnerability affects Mistral Vibe before 3.0.3 (including 2.25.8 and 2.26.1) and carries a severity score of 8.8 (CVSS 3.1) / 8.6 (CVSS 4.0, VulnCheck) (HIGH). Engineering and security operations teams running Mistral Vibe should prioritize upgrading to 3.0.3 or later.
Remediation & Patch Guidance
- Upgrade Mistral Vibe to 3.0.3 or later; do not stop at 2.25.7.
- Inspect .git/config for gpg.program and log.showSignature before opening unfamiliar projects.
- Keep approval prompts enabled while surveying untrusted repositories.
Frequently Asked Questions (CVE-2026-122135)
What versions are affected by CVE-2026-122135?
CVE-2026-122135 affects Mistral Vibe before 3.0.3 (including 2.25.8 and 2.26.1) in Mistral Vibe (Automatic git log / repository-configured gpg.program during project context).
How do I patch or remediate CVE-2026-122135?
Upgrade affected deployments to 3.0.3 or later and verify the remediation steps listed above.
What is the CVSS score of CVE-2026-122135?
CVE-2026-122135 is rated HIGH with a CVSS score of 8.8 (CVSS 3.1) / 8.6 (CVSS 4.0, VulnCheck) (vector: Crafted repo with gpg.program + log.showSignature and a signed commit; runs at session start before trust prompt).