Advisories
Security vulnerabilities, privacy incidents, safety concerns, and policy updates affecting LLMs and AI agents.
Security vulnerabilities, privacy incidents, safety concerns, and policy updates affecting LLMs and AI agents.
13 items
CVE-2026-116843 affects Mistral Vibe before 3.0.3. Attacker-defined git filter drivers in an untrusted repository's .git/config are executed when Vibe is started with --worktree, because git worktree add applies .gitattributes and runs filter smudge, clean, or process commands before the trusted-folder check. The result is execution of attacker commands with user privileges.
CVE-2026-109429 affects Mistral Vibe before 2.25.4 and contains a bypass of its command permission gate. Tree-sitter-bash static parsing misses a command substitution hidden inside a single-quoted variable value, which the attacker re-expands with the ${var@P} prompt-transform operator so bash's promptvars feature runs it at runtime. Only the trailing allowlisted command is classified, so arbitrary commands run silently with the privileges of the agent's terminal session.
Mistral Vibe before 2.25.5 has a permission validation bypass in the _extract_commands() function of bash.py. A parsing mismatch between tree-sitter-bash and bash over backslash-newline line continuations lets an attacker hide a command, such as a curl request, behind an allowlisted prefix like cd, so resolve_permission grants ALWAYS permission and bash runs unauthorized commands.
CVE-2026-67989 affects crmne/ruby_llm at commit fa6f279847d6d7027814539d9c0dfc3bbdfd2a83. The source describes a polynomial-time regular expression denial-of-service condition in Mistral model capability matching on Ruby 3.1.x.
Mistral Vibe before 2.25.5 contains a remote code execution flaw in its worktree creation process, which runs git hooks before trust validation. An attacker who supplies a repository with a crafted post-checkout hook can execute arbitrary shell commands with the privileges of the user running Vibe.
Fix: Fixed in 2.25.5. The source does not discuss any other mitigation.
NVD/CVE DatabaseAn arbitrary file access vulnerability in Mistral Vibe lets an attacker bypass workspace restrictions through commands classified as unconditionally allowed. Missing path validation for these commands allows access to files outside the active workspace without user approval.
CVE-2026-87987 is an arbitrary code execution vulnerability in Mistral Vibe that lets an attacker bypass command permission checks. Environment variable assignments placed before allowlisted commands are excluded from inspection, so attacker-controlled variables can trigger code execution without user approval.
CVE-2026-87986 is an arbitrary code execution vulnerability in Mistral Vibe. Attackers can bypass its command permission checks by using shell constructs the parser cannot interpret. Because the unparsed portions are omitted from inspection, embedded commands run on the user's system without approval.
An arbitrary code execution vulnerability in Mistral Vibe lets an attacker bypass command permission checks by using ANSI-C quoted arguments. These arguments are not properly inspected, so a crafted allowlisted command can run arbitrary code on the user's system without approval.
An arbitrary file write vulnerability in Mistral Vibe, introduced in version 1.3.4, lets an attacker create or overwrite files outside the active workspace without user approval. Shell redirection destinations are left out of permission checks, so otherwise allowlisted commands can write to any path the Vibe process can access.
An arbitrary file read vulnerability in Mistral Vibe, introduced in version 2.6.0, lets an attacker bypass workspace restrictions with quoted absolute paths in allowlisted shell commands. Improper handling of quotation marks during path validation allows files outside the active workspace to be read without user approval.
Compromised versions of @mistralai/mistralai (2.2.2, 2.2.3, 2.2.4), @mistralai/mistralai-azure and @mistralai/mistralai-gcp (1.7.1, 1.7.2, 1.7.3) were published to npm between May 11 at 22:45 UTC and May 12 at 01:53 UTC as part of a supply chain attack linked to the TanStack incident. The source says an affected developer device was involved and that Mistral infrastructure shows no sign of compromise. The embedded dropper is broken: setup.mjs references tanstack_runner.js while the payload is named router_init.js, so the payload never runs.
Fix: Stop using the affected package versions immediately. Clean systems where one of these packages has been installed. Check lockfiles, build artifacts, container images, package caches and private mirrors for affected versions, and remove the packages even though the dropper is broken.
The mistralai PyPI package version 2.4.6 contains a malicious dropper that runs on import on Linux. The code was added to src/mistralai/client/__init__.py and was not produced by the project's normal release pipeline, which uses PyPI Trusted Publishing. Versions 2.4.5 and earlier are not known to be affected.
Fix: Pin mistralai to 2.4.5 or earlier. While the PyPI project is quarantined, install from this repository at a known-good tag, e.g. git+https://github.com/mistralai/client-python.git@v2.4.5. On affected Linux hosts, rotate every credential reachable from the importing process and