mise has a local settings bypass config trust checks

The impact of CVE-2026-35533 is significant. An attacker who can inject a malicious .mise.toml file into a repository used by developers can gain control over the execution environment. This could allow them to execute arbitrary commands, steal sensitive data (API keys, credentials), or even compromise the entire development pipeline. The [env] _.source, templates, hooks, or tasks directives within the .mise.toml file provide avenues for malicious code injection. This vulnerability resembles supply chain attacks where malicious code is introduced through trusted dependencies or configuration files.

Developers using Mise to manage their dev tools are at risk, particularly those working in environments where they regularly clone repositories from external sources. Teams relying on shared repositories or automated build processes are especially vulnerable, as a malicious .mise.toml file could be silently introduced into their workflow. Users of older Mise versions who haven't implemented strict code review practices are also at increased risk.

• javascript / supply-chain:

Get-ChildItem -Path $env:USERPROFILE\Documents\*.mise.toml -Recurse | Select-String -Pattern '_.source = ' -ErrorAction SilentlyContinue

• javascript / supply-chain:

Get-ScheduledTask | Where-Object {$_.TaskName -like '*mise*'} | Format-List TaskName, Actions

• generic web:

curl -I https://your-mise-installation/ | grep -i 'Content-Type: application/toml'

1. 2026-04-07Disclosure

   disclosure

2. 2026-04-07Patch

   patch

1. आरक्षित2026-04-03
2. प्रकाशित2026-04-07
3. संशोधित2026-04-08
4. EPSS अद्यतन2026-04-15

The primary mitigation for CVE-2026-35533 is to upgrade to a patched version of Mise. Until an upgrade is possible, carefully scrutinize .mise.toml files from untrusted sources before incorporating them into your projects. Consider implementing a code review process specifically for these configuration files. If you are using a version control system, implement checks to prevent unauthorized modifications to .mise.toml files. As a temporary workaround, you could restrict the directories from which Mise loads .mise.toml files, though this may impact functionality. After upgrading, verify the fix by attempting to load a known malicious .mise.toml file and confirming that it is rejected.