Path Traversal in deepseek-tui (CVE-2026-75859)
Summary
Path traversal in deepseek-tui (CVE-2026-75859). Confidential information can be exposed externally. Exploitable via instructions. 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 validate file paths in the project config instructions field, allowing attackers to read arbitrary files on the victim's system. A malicious .codewhale/config.toml file in a cloned repository can specify paths outside the workspace that are read and injected into the AI system prompt for exfiltration.
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-75859 has been found in deepseek-tui.
Attackers can target a specific entry point like instructions over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/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-75859" on the vendor's site.
CVE-2026-75859 (deepseek-tui) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: instructions / expand_path / resolve_path / INSTRUCTIONS_FILE_MAX_BYTES
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.
Path traversal (CWE-22) exists in deepseek-tui. Attackers reach the vulnerable code path via instructions without authentication.
Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: instructions / expand_path / resolve_path / INSTRUCTIONS_FILE_MAX_BYTES.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
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