SSRF (Server-Side Request Forgery) in deepseek-tui (CVE-2026-75856)
Summary
SSRF in deepseek-tui (CVE-2026-75856). Confidential information can be exposed externally. Exploitable via mydomain.com. 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
DNS-pinning failure allows natural failure of code, however with a custom DNS server that fails the initial requests and allows the secondary requests, it's possible to bypass the logic.
Details
Simplified attack scenario:
- Attacker asks agent to visit the
mydomain.com. - CodeWhale tries to resolve the IP of
mydomain.com, however, the custom DNS server that's controlled by the attacker marks the request DNS query as failed (Time of Check). - CodeWhale allows the code to continue as it expects it request to fail again.
- On the secondary (Time of Use), the DNS server resolves mydomain.com to a local IP (e.g., 127.0.0.1)
- The request is executed and the content from port 80 is returned to the attacker, allowing full bypass of SSRF mitigations.
In the DNS-pinning section, when DNS fails, the code is allowed to continue as it's expected to fail. However
PoC
This is a custom DNS server that fails the first requests (in this case, the first and second requests must fail, while the 3rd and 4th are allowed due to…
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-75856 has been found in deepseek-tui.
Attackers can target a specific entry point like mydomain.com over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/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-75856" on the vendor's site.
CVE-2026-75856 (deepseek-tui) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: mydomain.com
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.
SSRF (CWE-918) exists in deepseek-tui. Attackers reach the vulnerable code path via mydomain.com without authentication.
Check the vendor advisory for the affected versions of deepseek-tui. Attack surface: mydomain.com.
Severity: High (CVSS 8.6/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 nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web vulncheck.com
- web github.com