← Back
CVE-2026-45310
high
CVSS 7.4
SSRF (Server-Side Request Forgery) in deepseek-tui (CVE-2026-45310)
Summary
SSRF in deepseek-tui (CVE-2026-45310). Confidential information can be exposed externally. Exploitable via ``fetch_url``. Mitigation: upgrade to `0.8.22` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45310** has been found in deepseek-tui.
Attackers can target a specific entry point like ``fetch_url`` 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.22** or later.
If unsure, ask your IT team or search "deepseek-tui CVE-2026-45310" on the vendor's site.
CVE-2026-45310 (deepseek-tui) — CWE-918 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `fetch_url` / `reqwest`
Patched: `0.8.22` — 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
**SSRF** (CWE-918) exists in deepseek-tui. Attackers reach the vulnerable code path via ``fetch_url`` without authentication.
📍 Affected scope
deepseek-tui — . Attack surface: `fetch_url` / `reqwest`.
🔥 Severity
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.8.22**.
🛡️ 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade deepseek-tui to 0.8.22ステージング環境で 0.8.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
deepseek-tui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.22"}]}]
rust
deepseek-tui-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.22"}]}]
npm
deepseek-tui
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.8.22"}]}]
crates.io
deepseek-tui
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.8.22"}]}]
crates.io
deepseek-tui-cli
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.8.22"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45310
- package https://github.com/Hmbown/DeepSeek-TUI
- web https://github.com/Hmbown/DeepSeek-TUI/security/advisories/GHSA-96ff-gc8g-wpvg
- web https://github.com/Hmbown/DeepSeek-TUI/releases/tag/v0.8.22
- web https://github.com/advisories/GHSA-96ff-gc8g-wpvg
- web https://github.com/Hmbown/CodeWhale/security/advisories/GHSA-96ff-gc8g-wpvg