Approved changes feed: RSS · Atom

cpe:2.3:a:jdx:mise:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorJdx (7357fe14-1218-523f-803c-08a53189db9a)
ProductMise (3d309d5d-bd11-5a51-90eb-da08cf405eee)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/jdx/mise purl2cpe 2026-06-01 10:11:00.269118

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-103929 vulnerable 2026-11-03 10:15:49.281194 mise permits untrusted local configuration to override default shell arguments
HIGH (7.8)
mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.7.14, in the default non-safe mode, mise loads .mise.toml [settings] from an untrusted local project before trust approval and strip_local_only_settings removes only fields marked global_only. The unix_default_file_shell_args, unix_default_inline_shell_args, windows_default_file_shell_args, and windows_default_inline_shell_args settings were not marked global_only, allowing a repository to replace the default interpreter arguments used by trusted tasks that have no explicit shell, postinstall directives, template exec operations, or hooks that fall back to the default shell. When mise appends the trusted command after the attacker-controlled interpreter arguments, the attacker-selected command can execute first with the developer account's privileges even though the local configuration was never trusted. The separate path-sanitization hardening note in the advisory is outside this vulnerability. This issue is fixed in version 2026.7.14.
Published: 2026-10-14T15:11:13.991Z
Updated: 2026-10-15T19:11:22.636Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-55448 vulnerable 2026-07-29 01:00:28.477711 mise: Local credential_command executes untrusted config
MEDIUM (6.3)
mise manages dev tools like node, python, cmake, and terraform. From 2026.3.15 until 2026.6.4, mise loads github.credential_command from local project config before any trust decision, then executes that value with sh -c when resolving a GitHub token. An attacker who can place a .mise.toml in a repository can execute arbitrary shell commands when the victim runs a GitHub-related mise command and no higher-priority GitHub token environment variable is set. This vulnerability is fixed in 2026.6.4.
Published: 2026-06-26T16:46:17.280Z
Updated: 2026-06-27T02:47:55.779Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-55441 vulnerable 2026-07-29 01:00:28.469755 mise: Arbitrary command execution via task-include files in an untrusted, config-less repository
HIGH (8.6)
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.
Published: 2026-06-26T16:48:23.194Z
Updated: 2026-06-26T18:41:26.486Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-54557 vulnerable 2026-07-29 01:00:27.890428 mise HTTP backend uses raw version path for install symlink destination
MEDIUM (5.5)
mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.6.1, the mise HTTP backend builds its install symlink destination from the raw resolved version string for non-latest versions. Normal tool install paths use the sanitized version pathname, but the HTTP backend's symlink path uses the raw value. On Unix-like systems, if that version is an absolute path, PathBuf::join discards the intended mise installs root. A repository-controlled .tool-versions file can therefore make mise install create a symlink outside the mise install tree. With bin_path, the same issue can place an executable symlink under an attacker-selected absolute prefix, such as a developer-tool prefix that is later added to PATH. This vulnerability is fixed in 2026.6.1.
Published: 2026-06-26T16:47:29.487Z
Updated: 2026-06-26T17:58:21.233Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-33646 vulnerable 2026-07-29 00:43:22.464366 mise: Arbitrary Code Execution via Tera Templates in .tool-versions Files (Trust Bypass)
CRITICAL (9.6)
mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.3.10, mise processes .tool-versions files through the Tera template engine during parsing, with the exec() function registered, enabling arbitrary command execution. Unlike .mise.toml files, .tool-versions files are not subject to trust verification in non-paranoid mode. This means an attacker can place a malicious .tool-versions file in a git repository, and when a victim with mise activated cds into the directory, arbitrary commands execute without any trust prompt. This vulnerability is fixed in 2026.3.10.
Published: 2026-06-26T16:51:44.261Z
Updated: 2026-06-29T13:28:19.212Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-35533 vulnerable 2026-06-08 07:59:14.086296 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.