{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-55441","id":"CVE-2026-55441","title":"mise: Arbitrary command execution via task-include files in an untrusted, config-less repository","description":"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 f","descriptionLong":"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-10-28T02:31:13.487469107Z","reserved":"2026-06-16T21:59:57.017Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","rating":"high","source":"GitHub_M"},"metrics":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","rating":"high","source":"GitHub_M"},{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","rating":"high","source":"github.com"},{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","rating":"high","source":"OSV"},{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","rating":"high","source":"GitHub"}],"rating":"high","products":["jdx mise"],"affectedProducts":[{"vendor":"jdx","product":"mise","defaultStatus":null,"versions":[{"version":"< 2026.6.4","status":"affected"}],"platforms":[]}],"packages":[{"ecosystem":"crates.io","name":"mise","purl":"pkg:cargo/mise","ranges":["<2026.6.4"],"fixed":["2026.6.4"],"advisory":"GHSA-77g9-363w-rccq"}],"cwes":["CWE-78","CWE-94","CWE-732"],"aliases":["GHSA-77g9-363w-rccq"],"references":[{"url":"https://github.com/jdx/mise/security/advisories/GHSA-77g9-363w-rccq","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55441.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55441","tags":["advisory"]},{"url":"https://github.com/jdx/mise","tags":["package"]}],"patchReferenced":false,"fixAvailable":true,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total"},"epss":0.00184,"epssPercentile":0.08055,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-55441","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55441","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-55441","ok":true,"note":"1 package"},{"name":"GitHub Advisory","url":"https://github.com/advisories/GHSA-77g9-363w-rccq","ok":true,"note":"GHSA-77g9-363w-rccq"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-55441","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}