{"answers":{"affected":"2 open source packages ship an affected version, including mise.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54557 exists.","fix":"Upgrade mise to 2026.6.1 or later.","what":"CVE-2026-54557 is a medium-severity path traversal 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-54557 and fix it if it is affected.\n\nWhat it is: CVE-2026-54557 is a medium-severity path traversal 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54557 exists.\n\nAffected packages and fixed versions:\n- mise (crates.io): affected all versions; fixed in 2026.6.1\n- mise (crates.io): affected all versions; fixed in 2026.6.1\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-54557/ (Markdown: https://insights.sbomify.com/CVE-2026-54557/index.md)","id":"CVE-2026-54557","markdown":"https://insights.sbomify.com/CVE-2026-54557/index.md","name":"CVE-2026-54557","record":{"aliases":["GHSA-f94h-j2qg-fxw3"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"mise dev tool manager","requires_auth":"none","summary":"Attackers can use a malicious .tool-versions file to create symlinks outside the install directory, potentially leading to code execution or privilege escalation.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mise HTTP backend uses raw version path for install symlink destination","id":"CVE-2026-54557","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"PocketSphinx: Buffer overflows in language and acoustic model loading code","id":"CVE-2026-54559"},"packages":[{"ecosystem":"crates.io","fixed":["2026.6.1"],"introduced":["0"],"last_affected":[],"package":"mise","purl":null,"source":"GHSA-f94h-j2qg-fxw3"},{"ecosystem":"crates.io","fixed":["2026.6.1"],"introduced":["0"],"last_affected":[],"package":"mise","purl":"pkg:cargo/mise","source":"GHSA-f94h-j2qg-fxw3"}],"prev":{"headline":"Http4s: HTTP/2 Denial of Service with Ember Backend","id":"CVE-2026-54556"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["jdx"]},"summary":"Attackers can use a malicious .tool-versions file to create symlinks outside the install directory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-54557/"}