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.
CVE-2026-54557
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EPSS
- 7.1%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 26, 2026mise HTTP backend uses raw version path for install symlink destination · Advisory · jdx/mise · GitHub
https://github.com/jdx/mise/security/advisories/GHSA-f94h-j2qg-fxw3Vendor Advisories for CVE-2026-54557(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 02:33 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 01:58 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:22 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 00:46 UTCEG score recompute
- 2026-07-03 00:05 UTCEG score recompute
- 2026-07-01 23:28 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 22:53 UTCEG score recompute
- 2026-06-29 22:17 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 21:42 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 21:07 UTCEG score recompute
Show 4 moreShow fewer
- 2026-06-26 20:29 UTCEG score recompute
- 2026-06-25 19:54 UTCEG score recompute
- 2026-06-24 19:19 UTCEG score recompute
- 2026-06-23 18:21 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54557?
When was CVE-2026-54557 disclosed?
Is CVE-2026-54557 actively exploited?
What is the CVSS score of CVE-2026-54557?
How do I remediate CVE-2026-54557?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54557
Is Your Infrastructure Affected by CVE-2026-54557?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.