CVE-2026-82533 — @deepseek-ai/dsh-client-c…
Fix: deepseek-ai/deepseek-harness@3e24087CVE-2026-82533 is a CWE-807 vulnerability in @deepseek-ai/dsh-client-connection. A fix is available for @deepseek-ai/dsh-client-connection — see the affected versions and patch details below.
DeepSeek Harness < 0.1.2-alpha.1 Authentication Bypass via Host Header Spoofing
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-82533.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@deepseek-ai/dsh-client-connectionnpmDescription
DeepSeek Harness before 0.1.2-alpha.1 contains an authentication bypass vulnerability that grants unauthenticated access to its local HTTP agent-control API by accepting a client-supplied loopback Host header in place of validating the actual TCP connection origin. On the default configuration, a confined tool-executed process can reach the loopback API without any port exposure and use it to escape its own OS sandbox, escalate to unconfined execution, and disable the approval prompt. When the port is externally reachable via tunnel, SSH forward, or reverse proxy, a remote attacker can exploit the same flaw to create sessions, execute arbitrary commands, and exfiltrate stored conversation transcripts without credentials.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @deepseek-ai/dsh-client-connection | all versions | 0.1.2-alpha.1npm install @deepseek-ai/dsh-client-connection@0.1.2-alpha.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @deepseek-ai/dsh-client-connection, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @deepseek-ai/dsh-client-connection to 0.1.2-alpha.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-82533 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-82533 in your dependencies?
Find it across npm, including transitive dependencies.