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

> Attackers can bypass trust checks in mise by placing a malicious config file, enabling execution of dangerous directives like hooks or tasks.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-436v-8fw5-4mj8

## What is CVE-2026-35533?

CVE-2026-35533 is a high-severity vulnerability in jdx mise, published on 7 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-35533?

2 open source packages ship an affected version, including mise. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mise` | crates.io | From 2026.2.18 | 2026.6.4 |
| `mise` | crates.io | From 2026.2.18 | 2026.6.4 |

Products: Jdx Mise.

## How do I fix CVE-2026-35533?

Upgrade mise to 2026.6.4 or later.

## Is CVE-2026-35533 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35533 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35533 and fix it if it is affected.

What it is: CVE-2026-35533 is a high-severity vulnerability in jdx mise, published on 7 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35533 exists.

Affected packages and fixed versions:
- mise (crates.io): affected from 2026.2.18; fixed in 2026.6.4
- mise (crates.io): affected from 2026.2.18; fixed in 2026.6.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35533/ (Markdown: https://insights.sbomify.com/CVE-2026-35533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35533
- OSV: https://osv.dev/vulnerability/CVE-2026-35533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35533/
Summaries are generated and may contain mistakes; the official description above is the record.