Categories
CVE-2026-75914 high CVSS 7.5

Path Traversal in deepseek-tui (CVE-2026-75914)

Summary

Path traversal in deepseek-tui (CVE-2026-75914). Confidential information can be exposed externally. Exploitable via Authorization header. 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 26de44a8bd5051f8f944ea60b2c37ae1d2b7d25e. Users should upgrade to 0.8.64 or later. The original reporter analysis is preserved below.

Summary

image_analyze follows workspace symlinks and leaks outside-workspace file bytes to the vision endpoint

The image_analyze tool resolves its image_path with a bare context.workspace.join instead of routing through ToolContext::resolve_path. The pre-join lexical check rejects absolute paths, Windows prefixes, and parent-dir components but never canonicalizes, so a symlink inside the workspace whose name ends in an image extension and whose target sits outside the workspace is read transparently. The tool has ReadOnly capability and the trait default makes it auto-approved, so the bypass executes with no user prompt.

Details

In crates/tui/src/vision/tools.rs (v0.8.37, lines 104-123):

async fn execute(&self, input: Value, context: &ToolContext) -> Result {
    let image_path = required_str(&input, "image_path")?;
    let prompt = input
        .get("prompt")
        .and_then(|v| v.as_str())
        .unwrap_or("Describe this image in detail.");

    let image_path_buf = Path::new(image_path);
    if image_path_buf.components().any(|c| {
        matches!(
            c,
            Component::Prefix(_) | Component::RootDir | Component::P…

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-75914 has been found in deepseek-tui.
Attackers can target a specific entry point like Authorization header 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-75914" on the vendor's site.

CVE-2026-75914 (deepseek-tui) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / read_image_file / Prefix / RootDir
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

Path traversal (CWE-22) exists in deepseek-tui. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: Authorization header / read_image_file / Prefix / RootDir.

🔥 Severity

Severity: High (CVSS 7.5/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.8.32"},{"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.8.32"},{"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