← Back
CVE-2026-33646
critical
CVSS 9.6
Code Injection in mise (CVE-2026-33646)
Summary
code injection in mise (CVE-2026-33646). Successful exploitation can lead to full system takeover. Exploitable via ``tera_exec``. Mitigation: upgrade to `2026.3.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33646** has been found in mise.
Attackers can target a specific entry point like ``tera_exec`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade mise to **2026.3.10** or later.
If unsure, ask your IT team or search "mise CVE-2026-33646" on the vendor's site.
CVE-2026-33646 (mise) — CWE-94 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `tera_exec` / `command` / `trust_check` / `mise_toml.rs`
Patched: `2026.3.10` — 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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in mise. Attackers reach the vulnerable code path via ``tera_exec`` without authentication.
📍 Affected scope
mise — . Attack surface: `tera_exec` / `command` / `trust_check` / `mise_toml.rs`.
🔥 Severity
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2026.3.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mise to 2026.3.10ステージング環境で 2026.3.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
mise
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.3.10"}]}]