New: the Agent Incident Ledger: disclosed incidents of AI gone rogueExplore the ledger
A “git status” command resolving to a red ./git.exe in the repository before reaching the installed Git on PATH.

A Cautionary Tale on Git Path Resolution: From Startup to Arbitrary Command Execution in Mistral Vibe (CVE-2026-122133)

Nov 16, 20264 Min

TL;DR

  • Manifold Security found a high-severity path resolution vulnerability in Mistral Vibe affecting Windows users, assigned CVE-2026-122133 (CVSS 3.1: 8.6).
  • Simply opening a malicious repository with Vibe, up to v2.25.4, was enough to execute arbitrary code on the host with the user’s privileges, at startup and before the user had approved anything. An attacker could use this to steal SSH keys, cloud credentials and API tokens, access the user’s other projects, or install persistence, all while Vibe appeared to start normally.
Split-screen Windows desktop: PowerShell shows a demo project containing git.exe and running vibe; Notepad windows show proof-of-execution logs written by the repository's own git.exe.

Introducing Mistral-Vibe

Vibe is Mistral AI's open source command-line coding assistant powered by their own models. Similar to other AI agent harnesses, it's a highly configurable CLI tool that allows users to interact with their projects using natural language. It packages familiar features such as subagents, task delegation, skills, and more.

How AI Agent Harnesses Use Git at Startup

Before we describe the vulnerability we found, let's first take a look at how AI agent harnesses use git. In our previous research, GitSpawn, we investigated what CLI AI harnesses do at startup. The common pattern we observed was that they run git in the background to gather information such as the current branch, the recent commits, and what is modified. Example git calls are below:

git status --porcelain git branch --show-current

Without exception, every harness we examined treats git as a dependency. That means any behaviour pertaining to git is worth investigating.

Resolving git.exe

Whenever a program is called, the operating system has to turn what was written into a real file on disk. How you write that name influences what the OS does next.

Let's look at Linux as an example. Below, both of these run git:

git status /usr/bin/git status

The first is the common form used to run git, its bare name. When called by its bare name, the OS walks the directories listed in PATH in order and runs the first git it finds. Some common directories found in PATH shipped in multiple Linux distros are: /usr/bin, /bin, and /usr/local/bin. These are system directories. The long form /usr/bin/git names the exact location, so no search happens at all.

Windows resolves a program call via its bare name differently from macOS or Linux. This is documented behaviour. A summarized version of the precedence order is as follows: the directory from which the application loaded, the current working directory for the parent process, system directories, and the directories listed in the PATH environment variable.

While looking at how mistral-vibe made its background git calls at startup, we observed that it spawned git by bare name and not a path to a known Git installation. This means the OS needs to resolve that name to a file on disk. On Linux and macOS that resolved through PATH as previously described. On Windows it meant that the lookup passed through the current directory of the calling process before reaching the real Git installation path. Because Vibe runs from the project you open, that current directory is the repository itself.

So on Windows, any project that shipped its own git.exe took precedence over the installed Git during Vibe's startup context gathering, before the user had approved any command. A malicious git.exe committed to a repository therefore achieved arbitrary command execution on the victim's machine the moment that project was opened. The binary ran with the full privileges of the user, so it could steal SSH keys, cloud and model-provider credentials, access tokens, or anything else the user could access.

Proof of Concept

The proof of concept we built was a repository with a tracked git.exe at its root. The binary simply appended a line recording the arguments it had been called with, then opened that file in Notepad. This executed on startup as soon as the user opened the project with vibe.

CVE-2026-122133: a repository's own git.exe executing at startup in Mistral Vibe.

We reported this to Mistral. They acknowledged it and shipped a fix in v2.25.5. VulnCheck assigned it CVE-2026-122133 (CVSS 3.1: 8.6).

The fix changed how Vibe decides what to run. It now resolves git to an absolute path before spawning it, skips PATH entries that are not absolute, and rejects any candidate found inside the project directory. The v2.25.5 CHANGELOG states it as: "Vibe no longer runs a project-local Git executable during automatic repository inspection."

What should users do? Update to v2.25.5 or later.

For developers: If your tool spawns other programs on Windows, don't rely on bare names. Resolve them to an absolute path from a trusted location, and never accept one found inside the project.

Securing the AI Ecosystem

At Manifold we look at the whole AI landscape rather than one tool at a time, because the weaknesses repeat across harnesses, tools and connectors. We track what has already gone wrong in the Agent Incident Ledger, we evaluate the components people install into their agents in Manifest, we publish agentaudit so anyone can see what a repository is able to make their coding agent do, and we keep breaking these products ourselves. The ecosystem is being assembled faster than it is being hardened. We would rather find these flaws than read about them.

More of our research:

About the author

  • Francisco Rosales

    Francisco Rosales

    Offensive Security Engineer

    Francisco Rosales is an Offensive Security Engineer specializing in application security across web, API, mobile, and AI-powered systems. He also builds AI-native tooling that bridges offensive security with modern AI workflows.