Categories
CVE-2026-75912 high CVSS 7.4

Vulnerability in deepseek-tui (CVE-2026-75912)

Summary

Vulnerability in deepseek-tui (CVE-2026-75912). Confidential information can be exposed externally. Exploitable via git_blame. 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 9a34b5034d29f05d1f28fa61b04719ca6a741020. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below.

Argument Injection in git_blame Tool Allows Arbitrary File Read Without Approval

Overview

The git_blame tool in DeepSeek-TUI passes the model-supplied rev parameter unvalidated into the argv of git blame. git blame accepts --contents=, which causes it to use the file's contents in place of the working tree and echo each line verbatim in the blame output. A rev value of --contents=/path/to/secret therefore exfiltrates the targeted file's contents into the tool result, which is returned to the model and displayed in the chat transcript.

The tool is registered with ApprovalRequirement::Auto and declares ToolCapability::ReadOnly. The read is in-scope for the capability label, but the target of the read is not the user expects git_blame to read files inside the workspace, not arbitrary paths on the host.

This is a sibling of the git_show argument-injection vulnerability filed separately, sharing the same root cause (missing --end-of-options sentinel and unvalidated rev).

Impact

Arbitrary file read at the privilege of the user running DeepSeek-TUI, via malicious repository content combined with prompt injection (the threat m…

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-75912 has been found in deepseek-tui.
Attackers can target a specific entry point like git_blame over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/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-75912" on the vendor's site.

CVE-2026-75912 (deepseek-tui) — CWE-88 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: git_blame / rev / git_show / fetch_url
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

A vulnerability (CWE-88) exists in deepseek-tui. Attackers reach the vulnerable code path via git_blame without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: git_blame / rev / git_show / fetch_url.

🔥 Severity

Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.

🔧 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":"SEMVER","events":[{"introduced":"0.3.27"},{"fixed":"0.8.41"}]}]
rust codewhale-tui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.64"}]}]
npm codewhale
[{"type":"SEMVER","events":[{"introduced":"0.8.41"},{"fixed":"0.8.64"}]}]
crates.io deepseek-tui
[{"type":"SEMVER","events":[{"introduced":"0.3.27"},{"last_affected":"0.8.41"}]}]
crates.io codewhale-tui
[{"type":"SEMVER","events":[{"introduced":"0.8.41"},{"fixed":"0.8.64"}]}]

References

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