Vulnerability in @deepseek-ai/dsh-client-connection (CVE-2026-82533)
Summary
Vulnerability in @deepseek-ai/dsh-client-connection (CVE-2026-82533). Successful exploitation can lead to full system takeover. Exploitable via Host header. Mitigation: upgrade to 0.1.2-alpha.1 or later.
Original description
The description as published by the source.
DeepSeek Harness before 0.1.2-alpha.1 contains an authentication bypass vulnerability in its local HTTP control-plane API that allows attackers to gain full agent control by supplying a spoofed Host header, as the server validates only the client-supplied Host header value rather than the actual TCP connection origin. Attackers can exploit this flaw to invoke privileged commands such as commands/execute with danger-full-access permissions, escalate session approval policies to unconfined execution, and retrieve all stored conversations without any credential or API key.
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-82533 has been found in @deepseek-ai/dsh-client-connection.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade @deepseek-ai/dsh-client-connection to 0.1.2-alpha.1 or later.
If unsure, ask your IT team or search "@deepseek-ai/dsh-client-connection CVE-2026-82533" on the vendor's site.
CVE-2026-82533 (@deepseek-ai/dsh-client-connection) — CWE-807 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Host header
Patched: 0.1.2-alpha.1 — 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.
A vulnerability (CWE-807) exists in @deepseek-ai/dsh-client-connection. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of @deepseek-ai/dsh-client-connection. Attack surface: Host header.
Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.
Update to 0.1.2-alpha.1.
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-ai/dsh-client-connection' . 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-ai/dsh-client-connection' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@deepseek-ai/dsh-client-connectionを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @deepseek-ai/dsh-client-connection to 0.1.2-alpha.1ステージング環境で 0.1.2-alpha.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web disclosure@vulncheck.com
- web vulncheck.com
- web nvd.nist.gov
- web ox.security
- web github.com