CVE Intelligence
Analysis AI-assisted

CVE-2026-33646: mise: code injection via malicious .tool-versions file (CWE-94)

The mise development tool manager processes .tool-versions files through a template engine before version 2026.3.10, which the record describes as enabling arbitrary command execution. According to the record, a victim with mise activated who enters a malicious repository can be affected without a trust prompt in non-paranoid mode. The record gives a CVSS 3.1 base score of 9.6 (Critical), and no confirmed exploitation appears in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

mise is a tool for managing development tools such as Node, Python, CMake and Terraform. According to the record, versions before 2026.3.10 process .tool-versions files through the Tera template engine during parsing, which can lead to arbitrary command execution.

Impact

  • The record describes arbitrary command execution affecting a user who has mise activated and changes into a malicious directory.
  • The weakness is classified as CWE-94 (Code Injection). The CNA published a CVSS 3.1 base score of 9.6 with Critical severity.
  • Unlike .mise.toml files, .tool-versions files are not subject to trust verification in non-paranoid mode, so the record describes no trust prompt before execution.

Affected products and versions

  • Product: mise, versions prior to 2026.3.10, as stated in the record description.
  • The record's structured affected and fixed lists are empty. The exact affected range should be confirmed in the GitHub security advisory.

Exploitation status

  • The record shows this CVE is not listed in CISA KEV. No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

  • Upgrade mise to version 2026.3.10 or later, which the record states contains the fix.
  • Until the upgrade is complete, avoid entering untrusted repositories on systems where mise is activated.
  • Review the GitHub security advisory for vendor guidance.

Detection guidance

  • Inspect .tool-versions files in repositories that are cloned or received from external sources, looking for unexpected template-like content.
  • Maintain an inventory of mise versions on developer workstations and CI runners to confirm which systems are below the fixed version.

Limitations of the available information

  • The record has no structured affected or fixed version data, so the version range relies on the description text.
  • The EPSS probability is 0.00685, but EPSS estimates exploitation likelihood and does not replace the severity assessment.
  • The record does not state whether paranoid mode fully prevents the issue. This is unknown from the available data.

Frequently asked questions

Which mise versions are affected?

According to the record description, versions prior to 2026.3.10 are affected. The structured affected list in the record is empty, so confirm the range in the GitHub advisory.

Is this vulnerability known to be exploited in the wild?

The record shows this CVE is not listed in CISA KEV, and no confirmed exploitation appears in the sources consulted.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.