VulnerabilityPublished 28 Sep 2026Updated 1 Oct 2026

CVE-2026-101132: deepseek-harness · Path Traversal

Affects deepseek-harnessSource CVE Database V5

Compare

Public exploit available · CVSS 2.3 Low.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-rh7q-h525-wx9f

What to do

Affected software

Product	Affected	Fixed in
DeepSeekdeepseek-harness	Affected =0.1.7-rc.0 =0.1.7-rc.1 =0.1.7-rc.2	Fixed in–
npmdeepseek-harness`pkg:npm/deepseek-harness`Other threats	Affected =0.1.7-rc.0 =0.1.7-rc.1 =0.1.7-rc.2	Fixed in–

CPE configurations (1)

cpe:2.3:a:deepseek:deepseek-harness:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor vendor communications for updates. Until a fix is released, restrict network access to the affected service where possible and consider additional application-layer protections to mitigate path traversal risks. Review and harden input validation for the dsh.bundle.patch argument if source code modifications are feasible.

Description

A path traversal vulnerability exists in DeepSeek deepseek-harness versions 0.1.7-rc.0, 0.1.7-rc.1, and 0.1.7-rc.2. The issue is in the loadProfile function of the Bundle Patch Handler component, allowing remote attackers to manipulate the dsh.bundle.patch argument to perform path traversal. Exploitation is difficult and requires a high level of complexity. The vendor has not responded to the disclosure, and no patch or fix is currently available. Public exploit code has been released, but no known active exploitation in the wild is reported. The CVSS 4.0 base score is 2.3, indicating low severity.

Impact

Successful exploitation allows an attacker to perform path traversal, potentially accessing files outside the intended directory scope. However, the overall impact is limited by the high complexity of the attack and the low CVSS score (2.3). There is no indication of privilege escalation, denial of service, or data modification beyond path traversal. No known active exploitation in the wild has been reported.

Summary

CVE-2026-101132 is a path traversal vulnerability in the loadProfile function within the packages/boot/app-boot/src/profile.ts file of the Bundle Patch Handler component in DeepSeek deepseek-harness. This flaw affects versions 0.1.7-rc.0, 0.1.7-rc.1, and 0.1.7-rc.2. The vulnerability arises from improper validation of the dsh.bundle.patch argument, which can be manipulated remotely to traverse directories. Exploitation complexity is high, and no privileges or user interaction are required, but the attack vector is network-based. The vendor was contacted but did not provide a response or patch. Public exploit code is available, though no active exploitation has been observed.

References

Community reviews

Loading reviews…