# CVE-2026-101102: deepseek-ai deepseek-harness Code Mode Sandbox run_code sandbox

> Attackers can bypass the code mode sandbox to execute arbitrary code, as the vendor explicitly states the sandbox is not a security boundary.

- **Severity:** Medium 5.3 (`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:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-m9ww-cpfc-8cf2

## What is CVE-2026-101102?

CVE-2026-101102 is a medium-severity vulnerability in deepseek-ai deepseek-harness, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in deepseek-ai deepseek-harness up to 0.1.0-rc.7. Impacted is the function run_code of the component Code Mode Sandbox. The manipulation results in sandbox issue. The attack can be executed remotely. The vendor's own code, SAFETY.md, and design notes all explicitly state the worker is "containment, not a security boundary". The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-265, CWE-264

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


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

No fix has been published for CVE-2026-101102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101102 being exploited?

There is no known exploitation of CVE-2026-101102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101102 and fix it if it is affected.

What it is: CVE-2026-101102 is a medium-severity vulnerability in deepseek-ai deepseek-harness, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101102 in the wild and no public exploit code.

Affected product: deepseek-ai deepseek-harness. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101102/ (Markdown: https://insights.sbomify.com/CVE-2026-101102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101102
- OSV: https://osv.dev/vulnerability/CVE-2026-101102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101102/
Summaries are generated and may contain mistakes; the official description above is the record.