LLaMA-Factory allows Code Injection through improper vhead_file safeguards

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

EPSS

• CVE-2025-53002: 1.27% estimated exploitation activity in the next 30 days; percentile 69.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A critical remote code execution vulnerability was discovered during the Llama Factory training process. This vulnerability arises because the vheadfile 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 vheadfile argument is loaded without the secure parameter weightsonly=True. Note: In torch versions <2.6, the default setting is weightsonly=False, and Llama Factory's setup.py only requires torch=2.0.0. Affected Version Llama Factory versions <=0.9.3 are affected by this vulnerability. Details 1. In LLaMA Factory's WebUI, when a user sets the Checkpoint path, it modifies the adapternameorpath parameter passed to the training process. code in src/llamafactory/webui/runner.py <img width="1040" alt="image-1"…

Published by the source

27 Jun 2025, 15:27 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xj56-p8mm-qmxj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xj56-p8mm-qmxj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53002

Advisory: LLaMA-Factory allows Code Injection through improper vhead_file safeguards
IDs: CVE-2025-53002, GHSA-xj56-p8mm-qmxj
Record: https://patchnext.com/advisories/cve-2025-53002 (revision 2, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI llamafactory: affected <= 0.9.3

## Suggested inspection (read-only)
- `python -m pip show llamafactory`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on llamafactory.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xj56-p8mm-qmxj (OSV record GHSA-xj56-p8mm-qmxj lists affected ranges: PyPI llamafactory >=0 <=0.9.3)
- Verified: https://github.com/advisories/GHSA-xj56-p8mm-qmxj (GitHub-reviewed advisory GHSA-xj56-p8mm-qmxj lists affected ranges: PyPI llamafactory >=0 <=0.9.3)

Commands are suggestions: review each one before running it.