Skip to main content

Jackrong Finetuning Guide CVE-2026-113738

| EUVDEUVD-2026-106991 LOW
Path Traversal (CWE-22)
2026-10-21 VulDB GHSA-q5q6-rw2f-74pm
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious weight_map with traversal shard_name
  2. Exploit
    Victim runs extract_mtp_heads pipeline
  3. Execution
    Path traversal resolves outside target dir
  4. Impact
    Read or overwrite unintended files

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that a victim invoke the extract_mtp_heads function in qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py against an attacker-influenced MTP weight_map whose shard_name value contains path-traversal sequences; the flaw is in the MTP weight_map Handler's handling of the shard_name argument. The key limiting factors are: user interaction is required (CVSS UI:P - a victim must run the pipeline on the crafted input), impact is limited to low confidentiality/integrity/availability, and there is no network-facing service implied - the 'remote' characterization most plausibly means delivery of a malicious model artifact rather than exploitation of a listening endpoint. No authentication is required per PR:N, but the dependence on local pipeline execution of untrusted input substantially narrows realistic exploitation.

Impact

This is a genuinely low-priority issue despite being a path traversal (CWE-22) with a publicly available PoC. The vendor-assigned CVSS 4.0 score is only 2.1, consistent with its low impact metrics (VC:L/VI:L/VA:L) and the UI:P requirement meaning exploitation is not fully autonomous - a user must process attacker-controlled input for the malicious shard_name to be parsed by extract_mtp_heads. It is NOT in CISA KEV, so there is no confirmed active exploitation, and no EPSS score was provided in the input, so widespread-exploitation probability cannot be quantified. The description's claim that the attack can be 'initiated remotely' conflicts with the actual mechanism: a path-traversal via a weight_map shard_name in a local Python finetuning pipeline is realistically a case of processing a crafted/malicious model artifact, not a network service - verify the true attack vector before treating this as a remote-exploitable flaw. Signals are consistent overall (low CVSS, PoC-only, no KEV), and the dominant risk driver is deployment footprint: this is an obscure personal GitHub guide repository with negligible production presence, so real-world risk is minimal.

Exploit ScenarioDerived

An attacker publishes or supplies a crafted model/weight artifact whose weight_map contains a shard_name with directory-traversal sequences (e.g. ../../). When a victim runs the qwen_mtp_gguf_pipeline.py extraction on that artifact, the unsanitized shard_name causes file reads or writes outside the intended directory. A public PoC (poc.zip) exists, but exploitation depends on the victim processing the attacker-supplied input (UI:P).

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Path traversal in the Jackrong Finetuning Guide's Qwen MTP GGUF pipeline lets an unauthenticated remote attacker supply a crafted MTP weight_map whose shard_name value contains traversal sequences, causing files outside the intended model directory to be accessed when a victim runs the extract_mtp_heads function. The affected code is qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py through commit ef2b17f2798cd18cd85375080c35a58397ad0d09, distributed as a rolling release with no tagged versions. Publicly available exploit code exists, but impact is limited to low confidentiality, integrity, and availability with required user interaction, and there is no CISA KEV listing at time of analysis.

RemediationAI

No vendor-released patch was identified at time of analysis; the maintainer was informed through https://github.com/R6410418/Jackrong-llm-finetuning-guide/issues/16 but had not responded, so there is no exact fixed version to cite. Until an upstream fix lands, locally patch extract_mtp_heads to reject absolute shard_name values and any path containing '..', normalize the candidate path, and verify with os.path.realpath that it remains under the expected model directory before opening it; the trade-off is that legitimate nested shard layouts may need an explicit allowlist. Avoid running the Qwen MTP GGUF pipeline against untrusted model artifacts, and when testing untrusted inputs run it in a least-privilege container with a read-only model mount and no access to secrets or sensitive host paths; this reduces impact but does not remove the flaw and may disrupt normal caching or write workflows. Track https://github.com/R6410418/Jackrong-llm-finetuning-guide/issues/16 and https://github.com/R6410418/Jackrong-llm-finetuning-guide/ for an upstream commit or release, and consult https://vuldb.com/vuln/422910 for updated advisory information.

Affected VersionsENISA

Jackrong-llm-finetuning-guide ef2b17f2798cd18cd85375080c35a58397ad0d09

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a CWE-22 path traversal in a Python model-processing pipeline for Qwen MTP GGUF artifacts. The extract_mtp_heads function consumes an MTP weight_map and uses the caller-supplied shard_name argument to locate shard files; without canonicalizing the resulting path and verifying it remains inside the expected model directory, values containing ../ sequences or absolute paths can escape that directory. The CPE identifies the R6410418 Jackrong-llm-finetuning-guide repository with a wildcard version because the project uses a rolling release model and does not publish tagged affected or fixed versions. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L) reflects that exploitation requires a victim to invoke the pipeline on an attacker-influenced model artifact; the 'remote' vector most plausibly describes delivery of a malicious weight_map rather than a listening network service, and no authentication is required per PR:N.

Know when Jackrong Llm Finetuning Guide gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 6.3 MEDIUM

A victim must run the pipeline on attacker-supplied model data (UI:R) which may be fetched remotely (AV:N); no auth needed (PR:N); traversal yields limited file read/write, so C/I/A all Low.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 21, 2026 - 01:23 NVD
MEDIUM LOW
CVSS changed
Oct 21, 2026 - 01:23 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 21, 2026 - 00:30 cve.org
LOW 2.1

DescriptionCVE.org

A vulnerability has been found in R6410418 Jackrong-llm-finetuning-guide up to ef2b17f2798cd18cd85375080c35a58397ad0d09. This vulnerability affects the function extract_mtp_heads of the file qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py of the component MTP weight_map Handler. The manipulation of the argument shard_name leads to path traversal. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Threat Intelligence Overview

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Rare
obscure personal GitHub finetuning-guide repo, negligible production footprint
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Related Vulnerabilities in Jackrong-llm-finetuning-guide Path Traversal Flaws

View all 2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy