CVE-2026-55441
HighCVSS 8.6Exploitation Probability (EPSS)
Low risk8th percentile — higher than 8% of all known CVEs
Summary
Vulnerability in mise (versions prior to 2026.6.4) allows remote code execution without user interaction. The trust mechanism does not cover task-include files, enabling arbitrary command execution via tera templates with exec() function. Simply entering a directory with a repository and listing tasks (e.g., mise tasks) or using Tab completion triggers the exploit.
Risk Assessment
An attacker can take control of the victim's system by placing a malicious task file in a repository. The victim does not need to execute any file – merely entering the directory and listing tasks (or pressing Tab) executes arbitrary code.
Recommendation
Immediately update mise to version 2026.6.4 or later. Until updated, avoid entering untrusted directories containing mise-tasks/ or .mise/tasks/ files.
Original NVD description (English source)
mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.6.4, mise's trust feature gates config files (mise.toml, .tool-versions) through trust_check, but task-include files are loaded on a path that never reaches it. When a directory has a task-include dir (mise-tasks/, .mise/tasks/, …) but no config file, mise falls back to the default includes and renders each task's tera fields — and that tera environment has exec() registered. A {{ exec(command='…') }} in any rendered field runs arbitrary commands the moment the tasks are merely listed. There's no config file to gate on, so no trust prompt ever appears. Read-only commands trigger it: mise tasks, mise task ls, mise run, mise tasks --usage (the query shell completion runs on Tab). The victim only has to cd into a cloned repo and list or tab-complete a task. This vulnerability is fixed in 2026.6.4.