Categories
CVE-2026-75858 high CVSS 7.8

Code Injection in deepseek-tui (CVE-2026-75858)

Summary

Code injection in deepseek-tui (CVE-2026-75858). Successful exploitation can lead to full system takeover. Exploitable via rlm_eval. Mitigation: upgrade to 0.8.41 or later.

Original description

The description as published by the source.

Maintainer resolution

The CodeWhale maintainers validated this report. The affected package ranges are recorded in the advisory metadata. Version 0.8.64 contains the fix in commit 57f3c89471e27ac4032d9791f6885e5d4408c381. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below.

Summary

The rlm_eval tool runs an arbitrary Python string chosen by the model in a real python3 interpreter. Its approval_requirement() returns ApprovalRequirement::Auto, which the engine treats as "never prompt," regardless of the user's configured --approval-policy. A single tool call — which prompt injection from any untrusted content the agent reads (a web page, a fetched URL, a repo file, an MCP tool result) can induce — runs code on the user's machine at the user's privilege with no prompt and no audit step. This is the same defect that was already patched on the sibling run_tests tool (CVE-2026-45311); the fix never reached rlm_eval or rlm_open, which expose a broader surface (full Python on the host, not just cargo test).

Details

rlm_eval's execute() reads the LLM-controlled code field and runs it (crates/tui/src/tools/rlm.rs:215-300):

fn capabilities(&self) -> Vec {
    vec![ToolCapability::Network, ToolCapability::ExecutesCode]
}

fn approval_requirement(&self) -> ApprovalRequirement {
    ApprovalRequirement::Auto          // overrides the safe default below
}

async fn execute(&self, input: Value, context:…

Source: NIST National Vulnerability Database 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-75858 has been found in deepseek-tui.
Attackers can target a specific entry point like rlm_eval over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade deepseek-tui to 0.8.41 or later.
If unsure, ask your IT team or search "deepseek-tui CVE-2026-75858" on the vendor's site.

CVE-2026-75858 (deepseek-tui) — CWE-94 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: rlm_eval / python3 / run_tests / rlm_open
Patched: 0.8.41 — 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 deepseek-tui. Attackers reach the vulnerable code path via rlm_eval without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: rlm_eval / python3 / run_tests / rlm_open.

🔥 Severity

Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.8.41.

🛡️ 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 'deepseek-tui' . 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 'deepseek-tui' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade deepseek-tui to 0.8.41

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

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

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

Affected packages

rust deepseek-tui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
npm deepseek-tui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.41"}]}]
rust codewhale-tui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.64"}]}]
npm codewhale
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.64"}]}]

References

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