Quick answers
- Is CVE-2026-93993 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93993 being exploited in the wild.
- How severe is CVE-2026-93993?
- High severity, with a CVSS score of 8.8, published 19 September 2026.
- Which products and versions are affected?
- Mistral Vibe before 2.25.5.
- Is there a fix for CVE-2026-93993?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93993 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-93993?
- 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.
Technical details
The vulnerability exists in the worktree creation process where git hooks (specifically post-checkout) are executed before trust validation occurs. An attacker can craft a repository containing a malicious post-checkout hook that executes arbitrary shell commands. The attack requires the user to clone or interact with the attacker-controlled repository through Mistral Vibe, and no network interaction is required beyond initial repository access.
Affected products
- Mistral Vibe before 2.25.5
Timeline
- 2026-09-19: disclosed