SSRF (Server-Side Request Forgery) in deepseek-tui (CVE-2026-45373)
Summary
SSRF in deepseek-tui (CVE-2026-45373). Confidential information can be exposed externally. Mitigation: upgrade to 0.8.26 or later.
Original description
The description as published by the source.
Summary
Although SSRF is validated against hostnames that resolve to private IPv6 addresses, when providing the IPV6 in URL as http://[::1], the SSRF defenses do not work.
Details
PoC
Prompt: Run fetch_url tool and give output, no thinking. Use url : http://[::1]
Impact
Access to local restricted resources
Source: GitHub Security Advisories (Global) 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-45373 has been found in deepseek-tui.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade deepseek-tui to 0.8.26 or later.
If unsure, ask your IT team or search "deepseek-tui CVE-2026-45373" on the vendor's site.
CVE-2026-45373 (deepseek-tui) — CWE-918 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.8.26 — 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.
SSRF (CWE-918) exists in deepseek-tui.
Check the vendor advisory for the affected versions of deepseek-tui.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 0.8.26.
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.26ステージング環境で 0.8.26 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com