{"answers":{"affected":"2 open source packages ship an affected version, including mise.","exploited":"There is no known exploitation of CVE-2026-55441 in the wild and no public exploit code.","fix":"Upgrade mise to 2026.6.4 or later.","what":"CVE-2026-55441 is a high-severity command injection vulnerability in jdx mise, published on 26 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-55441 and fix it if it is affected.\n\nWhat it is: CVE-2026-55441 is a high-severity command injection vulnerability in jdx mise, published on 26 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-55441 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mise (crates.io): affected all versions; fixed in 2026.6.4\n- mise (crates.io): affected all versions; fixed in 2026.6.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55441/ (Markdown: https://insights.sbomify.com/CVE-2026-55441/index.md)","id":"CVE-2026-55441","markdown":"https://insights.sbomify.com/CVE-2026-55441/index.md","name":"CVE-2026-55441","record":{"aliases":["GHSA-77g9-363w-rccq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Dev tool manager","requires_auth":"none","summary":"Attackers can execute arbitrary commands when victims list tasks in an untrusted repository due to missing trust checks on task-include files.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"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 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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mise: Arbitrary command execution via task-include files in an untrusted, config-less repository","id":"CVE-2026-55441","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Goobi viewer: cleanUpQuery double-brace bypass allows arbitrary Solr local-param injection","id":"CVE-2026-55442"},"packages":[{"ecosystem":"crates.io","fixed":["2026.6.4"],"introduced":["0"],"last_affected":[],"package":"mise","purl":null,"source":"GHSA-77g9-363w-rccq"},{"ecosystem":"crates.io","fixed":["2026.6.4"],"introduced":["0"],"last_affected":[],"package":"mise","purl":"pkg:cargo/mise","source":"GHSA-77g9-363w-rccq"}],"prev":{"headline":"Missing authorization in UFO","id":"CVE-2026-55440"},"products":["mise"],"published":"2026-06-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["jdx"]},"summary":"Attackers can execute arbitrary commands when victims list tasks in an untrusted repository due to missing trust checks on task-include files.","url":"https://insights.sbomify.com/CVE-2026-55441/"}