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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.1.2-alpha.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. DeepSeek Harness prior to 0.1.2-alpha.2, specifically commit 3e24087 Web profile HTTP and WebSocket RPC control plane is exposed
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
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.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.1.2-alpha.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Read the original 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 whether your setup matches what the bug needs.
DeepSeek Harness prior to 0.1.2-alpha.2, specifically commit 3e24087 Web profile HTTP and WebSocket RPC control plane is exposedUpgrade to a fixed version: 0.1.2-alpha.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- deepseek-ai deepseek-harness
fixed in 0.1.2-alpha.2
Evidence 3
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-82033
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-82033?
deepseek-harness: before 0.1.2-alpha.2.Source: cve.now feed data
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: vulncheck.com
How do I fix CVE-2026-82033?
Upgrade deepseek-harness to 0.1.2-alpha.2 or later. The facts list no workaround.Source: vulncheck.com