Quick answers
- Is CVE-2026-35533 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35533 being exploited in the wild.
- How severe is CVE-2026-35533?
- High severity, with a CVSS score of 7.7, published 7 April 2026.
- Which products and versions are affected?
- mise (crates.io) >= 2026.2.18, < 2026.6.4, SEMVER:introduced=2026.2.18,fixed=2026.6.4.
- Is there a fix for CVE-2026-35533?
- Yes. mise (crates.io): upgrade to 2026.6.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35533 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-35533?
- Check whether you run mise (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mise (crates.io): upgrade to 2026.6.4 or later
cargo update -p mise
Technical details
A vulnerability in mise versions 2026.2.18 through 2026.4.5 arises because the application loads trust-related settings (such as 'trusted_config_paths', 'yes', and 'ci') from a local '.mise.toml' file before performing a trust validation check. By setting 'trusted_config_paths = ["/"]' in a malicious configuration file, an attacker can force the application to treat the untrusted file as trusted. This bypass allows the execution of dangerous directives, including '[env] _.source', templates, hooks, or tasks, when a user interacts with the affected directory (e.g., via 'mise hook-env'). The issue is resolved in version 2026.6.4 by ignoring trust-control settings in non-global configuration files.
Affected products
- jdx mise 2026.2.18 - 2026.4.5
Identifiers
- CVE-2026-35533
- GHSA-436v-8fw5-4mj8
Timeline
- 2026-04-03: advisory: GitHub Security Advisory published by vendor
- 2026-04-07: disclosed: CVE published to NVD
- 2026-06-04: patched: Vendor released version 2026.6.4 to address the issue