# CVE-2026-113737: R6410418 Jackrong-llm-finetuning-guide qwen_mtp_gguf_pipeline.py validate_indexed_tensors path traversal


- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-hwcm-74ff-c2x9

## What is CVE-2026-113737?

CVE-2026-113737 is a medium-severity vulnerability in R6410418 Jackrong-llm-finetuning-guide, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-113737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113737 is a medium-severity vulnerability in R6410418 Jackrong-llm-finetuning-guide, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113737 exists.

Affected product: R6410418 Jackrong-llm-finetuning-guide. 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-113737/ (Markdown: https://insights.sbomify.com/CVE-2026-113737/index.md)
```

## Sources

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

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