CVE-2026-35533

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-07) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-19952 (ENISA EUVD) · GHSA-436v-8fw5-4mj8 (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.2%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. From 2026.2.18 through 2026.4.5, mise loads trust-control settings from a local project .mise.toml before the trust check runs. An attacker who can place a malicious .mise.toml in a repository can make that same file appear trusted and then reach dangerous directives such as [env] _.source, templates, hooks, or tasks.

CVSS v3
7.8
EG Score
7.8HIGHmedium 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.2%
EPSS %ILE
5th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 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.

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

April 7, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Local settings bypass config trust checks · Advisory · jdx/mise · GitHub

https://github.com/jdx/mise/security/advisories/GHSA-436v-8fw5-4mj8

Vendor Advisories for CVE-2026-35533(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—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—
  • 2026.2.18 up to 2026.6.4: fixed in 2026.6.4
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 99 of 212 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 10:09 UTCEG score recompute
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-25 14:32 UTCEG score recompute
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-24 00:44 UTCEG score recompute
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-18 03:44 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-17 15:19 UTCEG score recompute
  19. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-12 16:11 UTCEG score recompute
  25. 2026-10-11 19:53 UTCEG score recompute
Show 74 more
  1. 2026-10-11 17:07 UTCEG score recompute
  2. 2026-10-11 14:34 UTCEG score recompute
  3. 2026-10-10 22:47 UTCOSV refresh
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-21 10:49 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-02 08:44 UTCOSV refresh
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-16 07:54 UTCEG score recompute
  49. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-14 05:22 UTCEG score recompute
  52. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-08-12 19:37 UTCEG score recompute
  54. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-08-11 19:49 UTCEG score recompute
  56. 2026-08-11 03:12 UTCEG score recompute
  57. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-08-09 15:52 UTCEG score recompute
  59. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  60. 2026-08-09 04:54 UTCEG score recompute
  61. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-08-08 01:51 UTCEG score recompute
  63. 2026-08-07 14:53 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-08-05 23:57 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  68. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-08-03 22:17 UTCEG score recompute
  70. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  71. 2026-08-02 14:13 UTCEG score recompute
  72. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  73. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  74. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-35533?
CVE-2026-35533 is a high-severity vulnerability; its CVE record was published on April 7, 2026. mise manages dev tools like node, python, cmake, and terraform. From 2026.2.18 through 2026.4.5, mise loads trust-control settings from a local project .mise.toml before the trust check runs. An attacker who can place a malicious .mise.toml in a repository can make that same file appear trusted and…
When was the CVE record for CVE-2026-35533 published?
The CVE record for CVE-2026-35533 was published on April 7, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-35533 actively exploited?
CVE-2026-35533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35533?
CVE-2026-35533 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-35533?
A fix for CVE-2026-35533 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-35533 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-35533

Explore →

Is Your Infrastructure Affected by CVE-2026-35533?

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

Book a Demo →Browse All CVEs