mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.7.14, in the default non-safe mode, mise loads .mise.toml [settings] from an untrusted local project before trust approval and strip_local_only_settings removes only fields marked global_only. The unix_default_file_shell_args, unix_default_inline_shell_args, windows_default_file_shell_args, and windows_default_inline_shell_args settings were not marked global_only, allowing a repository to replace the default interpreter arguments used by trusted tasks that have no explicit shell, postinstall directives, template exec operations, or hooks that fall back to the default shell. When mise appends the trusted command after the attacker-controlled interpreter arguments, the attacker-selected command can execute first with the developer account's privileges even though the local configuration was never trusted. The separate path-sanitization hardening note in the advisory is outside this vulnerability. This issue is fixed in version 2026.7.14.
CVE-2026-103929
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 51EG Risk 51/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%The EG Score, 7.8 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 8th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 14, 2026
Last Modified
October 15, 2026
Advisory Details (4)
Auto-updated Oct 14, 2026v2026.7.14: Multi-asset GitHub installs, safer defaults, and Windows pip
Patch available: jdx/mise v2026.7.14
https://github.com/jdx/mise/releases/tag/v2026.7.14commit c6cd7a9a2ca5 (jdx/mise)
Fix landed in jdx/mise commit c6cd7a9a2ca5 — awaiting tagged release
https://github.com/jdx/mise/commit/c6cd7a9a2ca580918562566126646e5d04317895security(config): restrict default shell args to global config
Fix merged in jdx/mise PR #11293 on 2026-07-25 — awaiting tagged release
https://github.com/jdx/mise/pull/11293Untrusted local .mise.toml [settings] can set the shell-interpreter args (default_inline/default_file shell_args), giving arbitrary command execution, because those interpreter settings were left off the global_only denylist added for CVE-2026-55448 · Advisory · jdx/mise · GitHub
https://github.com/jdx/mise/security/advisories/GHSA-g74g-rg72-j2p3Vendor Advisories for CVE-2026-103929(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-15 19:39 UTCEG score recompute
- 2026-10-15 19:20 UTCEG score recompute
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-10-14 17:11 UTCEG score recompute
- 2026-10-14 15:26 UTCEG score recomputeFirst assessed: 7.8 HIGH
- 2026-10-14 15:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-103929?
When was the CVE record for CVE-2026-103929 published?
Is CVE-2026-103929 actively exploited?
What is the CVSS score of CVE-2026-103929?
How do I remediate CVE-2026-103929?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103929
Is Your Infrastructure Affected by CVE-2026-103929?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.