Code Injection in deepseek-tui (CVE-2026-75911)
Summary
Code injection in deepseek-tui (CVE-2026-75911). Successful exploitation can lead to full system takeover. Exploitable via exec_shell. Mitigation: upgrade to 0.8.41 or later.
Original description
The description as published by the source.
CodeWhale versions before 0.8.64 fail to properly validate the allow_shell configuration parameter from project config files, allowing attackers to enable arbitrary shell command execution by committing a malicious .codewhale/config.toml file to a repository. When a user clones and opens the repository in CodeWhale, the AI model gains access to exec_shell and task_shell tools, enabling execution of arbitrary shell commands on the victim's machine without explicit user consent.
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-75911 has been found in deepseek-tui.
Attackers can target a specific entry point like exec_shell 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-75911" on the vendor's site.
CVE-2026-75911 (deepseek-tui) — CWE-94 / CVSS v3 7.8
Attack vector: local / unauthenticated
Attack surface: exec_shell / approval_policy / sandbox_mode / allow_shell
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.
Arbitrary code execution (CWE-94) exists in deepseek-tui. Attackers reach the vulnerable code path via exec_shell without authentication.
Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: exec_shell / approval_policy / sandbox_mode / allow_shell.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 0.8.41.
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.41ステージング環境で 0.8.41 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com