dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-54557

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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.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.

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

The mise HTTP backend uses raw version strings to construct symlink destinations for non-latest tool versions, unlike other backends that sanitize the version pathname. On Unix systems, when PathBuf::join receives an absolute path as the version string, it discards the base install directory entirely. A malicious .tool-versions file in a repository can therefore trigger creation of symlinks to attacker-controlled absolute paths outside the mise installation tree, potentially placing executables in directories later added to PATH.

MitigationUpgrade to mise version 2026.6.1 or later. Until then, avoid using .tool-versions files from untrusted sources with the HTTP backend, and verify that no unexpected symlinks exist in PATH-adjacent directories.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 the installed mise version
    Run `mise --version` or `mise -V` to get the version number. Compare it to 2026.6.1 - versions below this are affected.
    Affected if The installed version is lower than 2026.6.1
  2. Identify if the HTTP backend is active
    Run `mise settings` or check configuration files for `backend = "http"` or HTTP-related tool source settings. Also check if any tools are installed via HTTP backend using `mise ls --installed`.
    Affected if The HTTP backend is configured as a tool source for installed tools
  3. Locate .tool-versions files in use
    Run `mise toolchain` or check for .tool-versions files in current directory and home directory. Inspect the version strings listed - look for entries starting with `/` that indicate absolute paths.
    Affected if A .tool-versions file contains version strings that are absolute paths (starting with /) rather than version numbers
  4. Inspect symlinks in PATH-adjacent directories
    Run `ls -la` on directories listed in your PATH, particularly common bin directories like `~/.local/bin`, `/usr/local/bin`, or directories under mise's installation root. Look for symlinks pointing to locations outside the mise installation tree.
    Affected if Symlinks exist in PATH directories that point to absolute paths outside the expected mise installation directory

You are affected if your mise version is below 2026.6.1, you use the HTTP backend, and either a malicious .tool-versions file with absolute paths was processed or unexpected symlinks to external paths exist in your PATH directories.

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.1 or later. Until then, avoid using .tool-versions files from untrusted sources with the HTTP backend, and verify that no unexpected symlinks exist in PATH-adjacent directories.

Recommended fix High confidence

2026.6.1

  1. Check the current installed version of mise by running: mise --version
  2. Upgrade mise to version 2026.6.1 or later by following the official installation method for your system (e.g., using the install script, Homebrew, or other package managers)
  3. Verify the upgrade was successful by running: mise --version
  4. Ensure your .tool-versions files in any repositories are reviewed for suspicious version entries before running mise install

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54557 — 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-54557 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