Vulnerability in mise (CVE-2026-35533)
Summary
Vulnerability in mise (CVE-2026-35533). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2026.6.4 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35533 has been found in mise.
Successful exploitation can lead to full system takeover. CVSS score: 7.7/10.
What to do: upgrade mise to 2026.6.4 or later.
If unsure, ask your IT team or search "mise CVE-2026-35533" on the vendor's site.
CVE-2026-35533 (mise) — CWE-284 / CVSS v3 7.7
Attack vector: local / unauthenticated
Patched: 2026.6.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in mise.
Check the vendor advisory for the affected versions of mise.
Severity: High (CVSS 7.7/10). Successful exploitation can lead to full system takeover.
Update to 2026.6.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
miseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mise to 2026.6.4ステージング環境で 2026.6.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com