Quick answers
- Is CVE-2026-82033 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82033 being exploited in the wild.
- How severe is CVE-2026-82033?
- High severity, with a CVSS score of 8.4, published 4 November 2026.
- Which products and versions are affected?
- DeepSeek Harness prior to 0.1.2-alpha.2.
- Is there a fix for CVE-2026-82033?
- Yes: fixed in 0.1.2-alpha.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82033 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-82033?
- Check whether you run DeepSeek Harness at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.1.2-alpha.2
Technical details
A missing authentication vulnerability in the HTTP and WebSocket RPC control plane allows unauthenticated access to session methods including session.create and session.prompt. Local attack vectors enable arbitrary command execution through the agent's bash and filesystem tools, session traffic interception over the event mux stream, and approval bypass via POST /api/respond using only rpcId, approvalId, and sessionId values. The vulnerability is fixed in version 0.1.2-alpha.2.
Affected products
- DeepSeek Harness prior to 0.1.2-alpha.2
Timeline
- 2026-11-04: disclosed