CVE-2026-103929

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-15. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-101154 (ENISA EUVD) · GHSA-g74g-rg72-j2p3 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v2026.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.14
GitHub commit

commit c6cd7a9a2ca5 (jdx/mise)

Fix landed in jdx/mise commit c6cd7a9a2ca5 — awaiting tagged release

https://github.com/jdx/mise/commit/c6cd7a9a2ca580918562566126646e5d04317895
GitHub pull request

security(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/11293
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Untrusted 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-j2p3

Vendor 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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustmise @ 2026.7.14 (fixes <= 2026.7.13)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
mise—
  • every version up to 2026.7.14: fixed in 2026.7.14
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 30× 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.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-g74g-rg72-j2p3 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-01 08:00 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-29 21:12 UTCEG score recompute
  8. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-22 20:26 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-18 05:09 UTCEG score recompute
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-15 19:39 UTCEG score recompute
Show 5 more
  1. 2026-10-15 19:20 UTCEG score recompute
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-14 17:11 UTCEG score recompute
  4. 2026-10-14 15:26 UTCEG score recomputeFirst assessed: 7.8 HIGH
  5. 2026-10-14 15:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-103929?
CVE-2026-103929 is a high-severity vulnerability; its CVE record was published on October 14, 2026. 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…
When was the CVE record for CVE-2026-103929 published?
The CVE record for CVE-2026-103929 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-103929 actively exploited?
CVE-2026-103929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103929?
CVE-2026-103929 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103929?
A fix for CVE-2026-103929 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-103929 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-103929

Explore →

Is Your Infrastructure Affected by CVE-2026-103929?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs