Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSupply crafted weight_map artifact
-
ExploitVictim runs GGUF conversion pipeline
-
ExecutionPath traversal in validate_indexed_tensors
-
ImpactRead/write files outside intended directory
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 | Requires that a victim process an attacker-influenced weight_map argument through the validate_indexed_tensors function in qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py - i.e., the attacker must get a crafted model/weight_map artifact into the victim's GGUF conversion workflow. Limiting factors: the CVSS vector requires passive user interaction (UI:P - the victim must actually run the conversion pipeline) and low-level privileges (PR:L), impact is limited to Low C/I/A with no scope change, and the affected code is a niche script used only by people converting Qwen MTP models to GGUF format, so realistic exposure is narrow. |
| Impact | This is a low-priority, low-real-risk issue despite being remotely reachable. The CVSS 4.0 base score is only 2.0, and the vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L) shows why: exploitation requires at least low-level privileges (PR:L), passive user interaction (UI:P - the victim must run the conversion pipeline on attacker-influenced input), and yields only Low confidentiality, integrity, and availability impact with no scope change. The exploit maturity is marked E:P (proof-of-concept), consistent with the published poc.zip, but there is NO CISA KEV listing and NO EPSS score provided in the input, so there is no signal of widespread or automated exploitation. Signals are internally consistent - low severity, PoC-only, no active-exploitation evidence - rather than conflicting. The one caveat: the description claims the attack 'may be performed from remote,' yet the flaw lives in a local data-processing function (validate_indexed_tensors operating on a weight_map), so the 'remote' characterization most realistically means an attacker supplies a crafted model/weight_map artifact that a victim then processes - verify the actual delivery path before treating this as truly network-exploitable. The affected product is an obscure individual GitHub repository with negligible production footprint, further lowering practical priority. |
| Exploit ScenarioDerived | An attacker publishes or supplies a malicious model artifact containing a crafted weight_map; a user who runs the qwen-mtp-gguf conversion pipeline on it triggers validate_indexed_tensors, which follows the traversal sequence to read or write files outside the intended directory. A public proof-of-concept (poc.zip) exists, but exploitation is bounded by low impact and the requirement that the victim actively process the attacker's input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Path traversal in the qwen-mtp-gguf conversion script within Jackrong-llm-finetuning-guide allows authenticated low-privileged remote attackers to manipulate the weight_map argument and direct file operations outside intended directories, but the victim must run the conversion pipeline. Impact is limited to low confidentiality and integrity effects with no scope change, and exposure is narrow because the affected code is a niche Qwen MTP-to-GGUF conversion utility; publicly available exploit code exists.
RemediationAI
No vendor-released patch was identified at the time of analysis, and the project has not responded to the issue report. Until a fix is available, avoid processing untrusted model directories or weight_map artifacts with the qwen-mtp-gguf pipeline; validate and canonicalize weight_map values against an allowlist and reject absolute paths, parent-directory sequences, and paths that resolve outside the expected model directory. Run the conversion pipeline in a sandboxed container with read-only mounts of only the required model files and least-privilege credentials, accepting the trade-off that sandboxing may require volume configuration and can slow large conversions. Restrict access to conversion hosts and monitor the project issue at https://github.com/R6410418/Jackrong-llm-finetuning-guide/issues/15 and the VulDB entry at https://vuldb.com/vuln/422909 for updates.
Affected VersionsENISA
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 CWE-22 path traversal in validate_indexed_tensors of qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py, a Python utility that converts Qwen MTP model artifacts to GGUF format. The weight_map argument is used in file-path handling without adequate canonicalization or confinement to an expected model directory, so a crafted weight_map can reference paths outside the intended location. The CPE cpe:2.3:a:r6410418:jackrong-llm-finetuning-guide:*:*:*:*:*:*:*:* identifies the repository as the affected product, and because the project uses a rolling release model, fixed or affected version identifiers are not published. Exploitation requires low-level privileges and passive user interaction, meaning the victim must actually process an attacker-influenced model or weight_map artifact through the conversion workflow.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Attacker-supplied weight_map is processed only when the victim runs the pipeline (UI:R) with some local/authenticated context (PR:L); traversal allows limited file read/write (C:L/I:L) but no availability impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A flaw has been found in R6410418 Jackrong-llm-finetuning-guide up to ef2b17f2798cd18cd85375080c35a58397ad0d09. This affects the function validate_indexed_tensors of the file qwen-mtp-gguf/scripts/qwen_mtp_gguf_pipeline.py. Executing a manipulation of the argument weight_map can lead to path traversal. The attack may be performed from remote. The exploit has been published and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-106989
GHSA-hwcm-74ff-c2x9
NVD
CVE.org
EPSS
VulDB
Exploit-DB