dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-55441

HIGH · 8.6 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

mise's task-include feature loads Tera templates from mise-tasks/ and .mise/tasks/ directories without the trust verification that applies to config files. When no config file exists, arbitrary commands in templates via {{ exec(command='…') }} execute simply by listing tasks, since the tera environment has exec() registered and no trust prompt appears.

MitigationUpgrade to mise version 2026.6.4 or later. Avoid running mise tasks, mise task ls, or tab-completion in untrusted repositories before upgrading.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if mise is installed and get its version
    Run `mise --version` to obtain the installed mise version number
    Affected if The installed version is earlier than 2026.6.4 (e.g., 2026.6.3, 2026.5.x, etc.)
  2. Locate task directories in the current project
    Look for directories named `mise-tasks/` or `.mise/tasks/` in the project root
    Affected if Either of these directories exist and contain task definition files (typically with .toml extension)
  3. Inspect task files for dangerous template syntax
    Search inside task files (*.toml) in mise-tasks/ or .mise/tasks/ for the pattern `exec(command=` which indicates Tera template execution
    Affected if Any task file contains `{{ exec(command='...') }}` or similar Tera template syntax with exec function calls
  4. Check for the presence of a mise config file
    Look for a mise configuration file (mise.toml or .mise.toml) in the project root
    Affected if No mise.toml or .mise.toml file exists in the project root - this is the condition where the trust verification bypass occurs
  5. Verify the task-include feature can be triggered
    Run `mise task ls` in the project directory to trigger task loading - if tasks are defined in mise-tasks/ or .mise/tasks/ without a config file, they will be loaded automatically
    Affected if Running `mise task ls` executes or displays tasks from mise-tasks/ or .mise/tasks/ when no config file exists

A user is affected if they have mise version earlier than 2026.6.4 installed, have task files in mise-tasks/ or .mise/tasks/ directories containing exec() template syntax, and lack a mise.toml/.mise.toml config file in the project root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to mise version 2026.6.4 or later. Avoid running mise tasks, mise task ls, or tab-completion in untrusted repositories before upgrading.

Recommended fix High confidence

2026.6.4 or later

  1. Verify the current installed version of mise by running: mise --version
  2. Upgrade mise to version 2026.6.4 or later. Use your package manager or reinstall from the official source (e.g., Homebrew: brew upgrade mise, or cargo: cargo install mise)
  3. After upgrading, verify the new version is installed: mise --version
  4. If you work with untrusted repositories containing task-include directories (mise-tasks/, .mise/tasks/), ensure you trust the source before running any mise task commands

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55441 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55441 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data