Categories
CVE-2026-55448 medium CVSS 6.3

OS Command Injection in mise (CVE-2026-55448)

Summary

OS command injection in mise (CVE-2026-55448). Confidential information can be exposed externally. Exploitable via mise. 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.3.15 until 2026.6.4, mise loads github.credential_command from local project config before any trust decision, then executes that value with sh -c when resolving a GitHub token. An attacker who can place a .mise.toml in a repository can execute arbitrary shell commands when the victim runs a GitHub-related mise command and no higher-priority GitHub token environment variable is set. This vulnerability is fixed in 2026.6.4.

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-55448 has been found in mise.
Attackers can target a specific entry point like mise over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade mise to 2026.6.4 or later.
If unsure, ask your IT team or search "mise CVE-2026-55448" on the vendor's site.

CVE-2026-55448 (mise) — CWE-78 / CVSS v3 6.3
Attack vector: local / unauthenticated
Attack surface: mise / github.credential_command / settings_file.settings / settings.github.credential_command
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.

❓ What is the problem

OS command injection (CWE-78) exists in mise. Attackers reach the vulnerable code path via mise without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mise. Attack surface: mise / github.credential_command / settings_file.settings / settings.github.credential_command.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.6.4.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'mise' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mise を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade mise to 2026.6.4

    ステージング環境で 2026.6.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust mise
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.6.4"}]}]
crates.io mise
[{"type":"SEMVER","events":[{"introduced":"2026.3.15"},{"fixed":"2026.6.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details