# CVE-2025-53002: LLaMA-Factory Remote Code Execution (RCE) Vulnerability

> Attackers can execute arbitrary code on the host system by providing a malicious checkpoint path via the WebUI interface in LLaMA-Factory.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-xj56-p8mm-qmxj, PYSEC-2026-1576

## What is CVE-2025-53002?

CVE-2025-53002 is a high-severity unsafe deserialization vulnerability in hiyouga LLaMA-Factory, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LLaMA-Factory is a tuning library for large language models. A remote code execution vulnerability was discovered in LLaMA-Factory versions up to and including 0.9.3 during the LLaMA-Factory training process. This vulnerability arises because the `vhead_file` is loaded without proper safeguards, allowing malicious attackers to execute arbitrary malicious code on the host system simply by passing a malicious `Checkpoint path` parameter through the `WebUI` interface. The attack is stealthy, as the victim remains unaware of the exploitation. The root cause is that the `vhead_file` argument is loaded without the secure parameter `weights_only=True`. Version 0.9.4 contains a fix for the issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-53002?

3 open source packages ship an affected version, including llamafactory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `llamafactory` | PyPI | All versions to 0.9.3 | None |
| `llamafactory` | PyPI | All versions to 0.9.3 | None |
| `llamafactory` | PyPI | All versions to 0.9.3 | None |

Products: Hiyouga Llama-Factory.

## How do I fix CVE-2025-53002?

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

## Is CVE-2025-53002 being exploited?

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

## Other vulnerabilities in hiyouga LLaMA-Factory

- [CVE-2026-58116](https://insights.sbomify.com/CVE-2026-58116/): LLaMA-Factory 0.9.5 Remote Code Execution via WebUI Model Path (critical 9.3)
- [CVE-2025-61784](https://insights.sbomify.com/CVE-2025-61784/): LLaMA Factory's Chat API has Critical SSRF and LFI Vulnerabilities (high 7.6)
- [CVE-2024-52803](https://insights.sbomify.com/CVE-2024-52803/): LLama Factory Remote OS Command Injection Vulnerability (high 7.5)
- [CVE-2025-46567](https://insights.sbomify.com/CVE-2025-46567/): LLaMA-Factory Allows Arbitrary Code Execution via Unsafe Deserialization in Ilamafy_baichuan2.py (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53002 and fix it if it is affected.

What it is: CVE-2025-53002 is a high-severity unsafe deserialization vulnerability in hiyouga LLaMA-Factory, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53002 exists.

Affected packages and fixed versions:
- llamafactory (PyPI): affected all versions up to 0.9.3; no fix listed
- llamafactory (PyPI): affected all versions up to 0.9.3; no fix listed
- llamafactory (PyPI): affected all versions up to 0.9.3; no fix listed

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

## Sources

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

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