<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Mise (&lt; 2026.3.10) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/mise--2026.3.10/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 03 Jul 2026 11:07:52 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/mise--2026.3.10/feed.xml" rel="self" type="application/rss+xml"/><item><title>Mise Vulnerable to Arbitrary Code Execution via Tera Templates in .tool-versions Files (Trust Bypass)</title><link>https://feed.craftedsignal.io/briefs/2026-07-mise-rce-tool-versions/</link><pubDate>Fri, 03 Jul 2026 11:07:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-mise-rce-tool-versions/</guid><description>A critical vulnerability (CVE-2026-33646) in Mise allows for arbitrary code execution on victim machines via malicious `.tool-versions` files containing Tera template syntax, which are processed without trust verification, enabling silent supply chain attacks upon directory entry.</description><content:encoded><![CDATA[<p>A critical vulnerability, tracked as CVE-2026-33646, affects Mise, a popular multi-tool version manager. This flaw allows for arbitrary code execution on user systems when processing <code>.tool-versions</code> files. Unlike <code>.mise.toml</code> files, <code>.tool-versions</code> are not subject to a trust verification mechanism in non-paranoid mode (which is the default). This means an attacker can embed malicious Tera template syntax, specifically using the <code>exec()</code> function, into a <code>.tool-versions</code> file within a Git repository. When a victim, with <code>mise</code> activated, changes directory (<code>cd</code>) into such a repository, the malicious commands execute silently and automatically, leveraging the full privileges and environment variables of the current user. The vulnerability affects Mise versions prior to 2026.3.10 and poses a significant supply chain risk to developers.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts a malicious <code>.tool-versions</code> file containing <code>Tera</code> template syntax with an <code>exec()</code> function call (e.g., <code>{{ exec(command=&quot;malicious_command&quot;) }}</code>) and embeds it in a Git repository.</li>
<li>The victim, who has <code>mise</code> activated in their shell (e.g., <code>eval &quot;$(mise activate zsh)&quot;</code>), clones or downloads this malicious Git repository.</li>
<li>The victim navigates into the cloned repository's directory using a command like <code>cd</code>.</li>
<li>Mise's shell hook (<code>hook-env</code>) automatically triggers, initiating the parsing of configuration files, including the malicious <code>.tool-versions</code> file.</li>
<li>During parsing, the <code>ToolVersions::parse_str</code> function processes the <code>.tool-versions</code> file content through the <code>Tera</code> template engine without performing a trust check.</li>
<li>The <code>Tera</code> engine evaluates the embedded <code>exec()</code> function, which in turn spawns a shell process to execute the attacker-defined arbitrary command (e.g., <code>curl</code> for exfiltration or <code>id</code> for reconnaissance).</li>
<li>The malicious command executes silently as the victim's current user with their full environment, without any warning or user interaction.</li>
<li>This allows the attacker to achieve arbitrary code execution, potentially leading to data exfiltration, further compromise, or system modification, as demonstrated by the PoC's <code>curl</code> or <code>id</code> commands.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The successful exploitation of CVE-2026-33646 leads to arbitrary code execution on the victim's machine. This presents a critical supply chain attack vector, as <code>.tool-versions</code> files are commonly committed to repositories and are expected to be benign. Execution occurs silently without any user prompt or warning, running with the full privileges and environment of the current user. This allows attackers to perform actions such as credential theft by exfiltrating environment variables (which may contain tokens, API keys, or SSH agent information) or establishing further persistence. The widespread use of <code>mise</code> in development environments means a broad range of open-source projects and developer machines are potentially vulnerable.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2026-33646 by updating <code>mise</code> to version 2026.3.10 or newer immediately.</li>
<li>Deploy the provided Sigma rule to detect suspicious <code>curl</code> commands used for data exfiltration, often indicative of arbitrary code execution.</li>
<li>Enable <code>process_creation</code> logging for shell processes (<code>bash</code>, <code>zsh</code>, <code>powershell</code>, <code>cmd.exe</code>) to capture commands executed in user environments, especially in newly cloned or untrusted repositories.</li>
<li>Review and implement the recommended trust checks for <code>.tool-versions</code> files if patching is not immediately feasible.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>mise</category><category>rce</category><category>supply-chain</category><category>trust-bypass</category><category>code-execution</category><category>developer-tools</category><category>cve</category></item></channel></rss>