Code Injection in deepseek-tui (CVE-2026-45311)
Summary
Code injection in deepseek-tui (CVE-2026-45311). Successful exploitation can lead to full system takeover. Exploitable via run_tests. Mitigation: upgrade to 0.8.23 or later.
Original description
The description as published by the source.
CodeWhale is a DeepSeek + MiMo coding agent in terminal. From 0.3.0 to 0.8.23, the run_tests tool executes cargo test in the workspace with ApprovalRequirement::Auto, meaning it runs without any user approval prompt. cargo test compiles and executes arbitrary code: test binaries, build.rs build scripts, and proc macros. While auto-approving test execution is a deliberate design choice, it creates an inconsistency in the security boundary. However, in a malicious repository, test code can execute arbitrary shell commands, exfiltrate credentials, or establish persistence with zero approval. The attack is amplified by AGENTS.md (auto-loaded into the system prompt), which can instruct the model to run tests proactively at session start. This vulnerability is fixed in 0.8.23.
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-45311 has been found in deepseek-tui.
Attackers can target a specific entry point like run_tests over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade deepseek-tui to 0.8.23 or later.
If unsure, ask your IT team or search "deepseek-tui CVE-2026-45311" on the vendor's site.
CVE-2026-45311 (deepseek-tui) — CWE-94 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: run_tests / build.rs / AGENTS.md / Cargo.toml
Patched: 0.8.23 — 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.
Arbitrary code execution (CWE-94) exists in deepseek-tui. Attackers reach the vulnerable code path via run_tests without authentication.
Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: run_tests / build.rs / AGENTS.md / Cargo.toml.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to 0.8.23.
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 '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
-
1Identify exposure identify
grep -r 'deepseek-tui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
deepseek-tuiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade deepseek-tui to 0.8.23ステージング環境で 0.8.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com