CVE-2026-54557

mise HTTP backend uses raw version path for install symlink destination

Published Jun 26, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability lies in mise’s HTTP backend, which builds the symlink destination for installed tools using the raw resolved version string for non‑latest releases. Because this raw value can be an absolute path, the backend may create symlinks outside the intended installation tree. The flaw enables an attacker to place executable symlinks in arbitrary locations if they control a repository’s .tool-versions file or the bin_path configuration. The weakness is a classic path traversal (CWE‑22) that can lead to unauthorized file system modifications or unintended code execution by spoiling environment paths. The CVSS score of 5.5 reflects moderate risk for local systems.

Affected Systems

All installations of the jdx open-source tool manager 'mise', specifically any deployment running a version earlier than 2026.6.1. The issue impacts versions that use the HTTP backend for tool installation. Users of the latest release (2026.6.1 or later) are no longer affected.

Risk and Exploitability

The CVSS score of 5.5 indicates a medium severity vulnerability when it comes to privilege level and affected scope. No EPSS score is available, so the exploitation probability is unknown at this time, and it is not listed in the CISA KEV catalog. The likely attack vector would require local compromise or control over a repository from which mise downloads the .tool-versions file; from there, an attacker could craft absolute path strings that force symlink creation outside the installation directory. The resulting arbitrary symlink could point to an attacker‑controlled executable that would run when added to the user’s PATH, enabling privilege escalation or malicious code execution.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade mise to version 2026.6.1 to apply the fix that sanitizes the symlink destination.
  • Ensure that any .tool-versions file or bin_path configuration does not contain absolute path strings; use relative paths or curated repositories only.
  • Limit or audit the PATH environment variable so that unexpected executable directories created by symlinks are not invoked; consider isolating tool installation paths within a controlled environment.

Generated by OpenCVE AI on June 26, 2026 at 19:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-f94h-j2qg-fxw3 mise HTTP backend uses raw version path for install symlink destination
History
Type Values Removed Values Added
First Time appeared Jdx
Jdx mise
Vendors & Products Jdx
Jdx mise
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title mise HTTP backend uses raw version path for install symlink destination
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jun 26, 2026, 5:58 PM
Reserved
Jun 15, 2026, 7:04 PM
Status
Deferred
Published
Jun 26, 2026, 6:17 PM
Modified
Oct 25, 2026, 5:10 PM