CVE-2026-101102: deepseek-harness · Sandbox Issue
Affects deepseek-harnessSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:XExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| deepseek-aideepseek-harness | Affected
| Fixed in– |
npmdeepseek-ai/deepseek-harnesspkg:npm/deepseek-ai/deepseek-harnessOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:deepseek-ai:deepseek-harness:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor has not responded to the disclosure. Users should consider the sandbox as a containment mechanism only and not rely on it for security isolation. Until a patch or official guidance is provided, avoid running untrusted code in the sandbox or implement additional security controls outside of the sandbox environment.
Description
CVE-2026-101102 is a medium severity vulnerability in deepseek-ai deepseek-harness versions 0.1.0-rc.0 through 0.1.0-rc.7. It affects the run_code function in the Code Mode Sandbox component, resulting in a sandbox issue that can be exploited remotely. The vendor explicitly states that the sandbox is for containment only and not a security boundary. There is no vendor response or patch available at this time.