# CVE-2026-101078: deepseek-ai deepseek-harness Landlock Backend profiles.ts isolation

> Local attackers can bypass Landlock sandbox isolation in deepseek-harness, potentially escalating privileges or escaping the sandbox environment.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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-23q9-h232-4q79

## What is CVE-2026-101078?

CVE-2026-101078 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 has been found in deepseek-ai deepseek-harness up to 0.1.7-rc.2. Affected is an unknown function of the file packages/sandbox/sandbox-local/src/profiles.ts of the component Landlock Backend. Such manipulation leads to improper isolation or compartmentalization. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. It is advisable to implement a patch to correct this issue. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

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


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

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

## Is CVE-2026-101078 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101078 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101078 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101078 exists.

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-101078/ (Markdown: https://insights.sbomify.com/CVE-2026-101078/index.md)
```

## Sources

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

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