Quick answers
- Is CVE-2026-116843 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116843 being exploited in the wild.
- How severe is CVE-2026-116843?
- High severity, with a CVSS score of 8.8, published 27 October 2026.
- Which products and versions are affected?
- Mistral Vibe before 3.0.3.
- Is there a fix for CVE-2026-116843?
- Yes: fixed in 3.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116843 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116843?
- Check whether you run Mistral Vibe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.0.3
Technical details
The vulnerability exists in the worktree.py component where git filter drivers defined in .git/config are executed before the trusted-folder check occurs. When the --worktree flag is used with untrusted repositories, git applies .gitattributes and runs filter smudge, clean, or process commands, allowing arbitrary command execution. The fix implemented in version 3.0.3 reorders security checks to validate repository trust before applying git filters.
Affected products
- Mistral Vibe before 3.0.3
Timeline
- 2026-10-27: disclosed
- 2026-10-26: patched: v3.0.3 released