# CVE-2026-101131: deepseek-ai deepseek-harness dsh index.ts reliance on untrusted inputs in a security decision

> Local attackers can bypass security decisions by manipulating the E2B_API_KEY argument in the deepseek-harness library.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-vcc3-4jvw-qx89

## What is CVE-2026-101131?

CVE-2026-101131 is a medium-severity vulnerability in deepseek-ai deepseek-harness, published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in deepseek-ai deepseek-harness up to 0.1.5-rc.3. Impacted is an unknown function of the file packages/e2b/e2b/src/index.ts of the component dsh. The manipulation of the argument E2B_API_KEY leads to reliance on untrusted inputs in a security decision. Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-101131 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101131 is a medium-severity vulnerability in deepseek-ai deepseek-harness, published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101131 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-101131/ (Markdown: https://insights.sbomify.com/CVE-2026-101131/index.md)
```

## Sources

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

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