Mise vulnerable to arbitrary command execution via task-include files in an untrusted, config-less repository

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.6 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-55441: 0.18% estimated exploitation activity in the next 30 days; percentile 8.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary mise's trust feature gates config files (mise.toml, .tool-versions) through trustcheck, 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 Details Trust is enforced only inside config-file parsing: - src/config/configfile/misetoml.rs:276 — MiseToml::fromstr → trustcheck(path)? - src/config/configfile/toolversions.rs:62 — .tool-versions parser → trustcheck(&path)? -…

Published by the source

23 Jun 2026, 18:24 UTC

Last modified by the source

23 Jun 2026, 18:24 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-77g9-363w-rccq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55441

Advisory: Mise vulnerable to arbitrary command execution via task-include files in an untrusted, config-less repository
IDs: CVE-2026-55441, GHSA-77g9-363w-rccq
Record: https://patchnext.com/advisories/cve-2026-55441 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mise 2026.6.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io mise: affected < 2026.6.4; fixed in 2026.6.4

## Suggested inspection (read-only)
- crates.io mise: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-77g9-363w-rccq (GitHub-reviewed advisory GHSA-77g9-363w-rccq lists affected ranges: crates.io mise >=0 <2026.6.4)

Commands are suggestions: review each one before running it.