Live › vulnerability › CVE-2026-116843
Go to dashboardMistral Vibe before 3.0.3 reads git filter driver definitions from an untrusted repository's .git/config when started with --worktree. The attacker's smudge, clean or process commands run with the user's privileges before the trusted-folder check.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 01:34 UTC. All times on this page are UTC.
Developers who run Mistral Vibe with the --worktree option on repositories they did not write, such as cloned third-party code or pull request branches. Teams that only use Mistral Vibe on trusted repositories they control, or on versions 3.0.3 and later, are not exposed by this flaw.
No product ranges from the sources yet.
vibe --version (exact command unknown; confirm in the package manifest)--worktree flag in shell history or launch scripts.git/config for filter.* entries with smudge, clean or process commands3.0.3 or later--worktree on repositories you did not createEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116843")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.