Mistral Vibe before 3.0.3 RCE via Git Filter Drivers in Worktree Mode
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Mistral Vibe, a command-line coding tool, is affected by this vulnerability. An attacker who supplies a malicious repository can get commands executed with the user's privileges when the tool is run in worktree mode, because Git filter drivers defined in the repository's configuration run before the tool's trusted-folder check.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Mistral Vibe before 3.0.3 contains a remote code execution vulnerability that allows attackers to run commands by defining git filter drivers in an untrusted repository's .git/config. When started with --worktree, git worktree add applies .gitattributes and runs filter smudge, clean, or process commands before the trusted-folder check, executing attacker commands with user privileges.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- mistralai mistral-vibe
fixed in 3.0.3