FKIE_CVE-2026-54557
Vulnerability from fkie_nvd - Published: 2026-06-26 18:17 - Updated: 2026-10-25 17:10| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "mise",
"vendor": "jdx",
"versions": [
{
"status": "affected",
"version": "\u003c 2026.6.1"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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."
},
{
"lang": "es",
"value": "mise gestiona herramientas de desarrollo como node, python, cmake y terraform. Antes de 2026.6.1, el backend HTTP de mise construye el destino de su enlace simb\u00f3lico de instalaci\u00f3n a partir de la cadena de versi\u00f3n resuelta en bruto para versiones no m\u00e1s recientes. Las rutas de instalaci\u00f3n de herramientas normales utilizan el nombre de ruta de versi\u00f3n saneado, pero la ruta del enlace simb\u00f3lico del backend HTTP utiliza el valor en bruto. En sistemas tipo Unix, si esa versi\u00f3n es una ruta absoluta, PathBuf::join descarta la ra\u00edz de instalaciones de mise prevista. Un archivo .tool-versions controlado por el repositorio puede, por lo tanto, hacer que mise install cree un enlace simb\u00f3lico fuera del \u00e1rbol de instalaci\u00f3n de mise. Con bin_path, el mismo problema puede colocar un enlace simb\u00f3lico ejecutable bajo un prefijo absoluto seleccionado por el atacante, como un prefijo de herramienta de desarrollo que se a\u00f1ade posteriormente a PATH. Esta vulnerabilidad se corrige en 2026.6.1."
}
],
"id": "CVE-2026-54557",
"lastModified": "2026-10-25T17:10:00.197",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-54557",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-06-26T17:57:43.960724Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-06-26T18:17:00.553",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/jdx/mise/security/advisories/GHSA-f94h-j2qg-fxw3"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"url": "https://github.com/jdx/mise/security/advisories/GHSA-f94h-j2qg-fxw3"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.