← Back
CVE-2025-53002
Code Injection in llamafactory (CVE-2025-53002)
Summary
code injection in llamafactory (CVE-2025-53002). Confidential information can be exposed externally. Exploitable via ``vhead_file``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-53002** has been found in llamafactory.
Attackers can target a specific entry point like ``vhead_file`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "llamafactory CVE-2025-53002" on the vendor's site.
CVE-2025-53002 (llamafactory) — CWE-94 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `vhead_file` / `WebUI` / `setup.py` / `adapter_name_or_path`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in llamafactory. Attackers reach the vulnerable code path via ``vhead_file`` without authentication.
📍 Affected scope
llamafactory — . Attack surface: `vhead_file` / `WebUI` / `setup.py` / `adapter_name_or_path`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'llamafactory' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llamafactory' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `llamafactory` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
llamafactory
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.9.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-53002
- advisory https://github.com/advisories/GHSA-xj56-p8mm-qmxj
- package https://github.com/hiyouga/LLaMA-Factory
- package https://pypi.org/project/llamafactory
- web https://github.com/hiyouga/LLaMA-Factory/security/advisories/GHSA-xj56-p8mm-qmxj
- web https://github.com/hiyouga/LLaMA-Factory/commit/bb7bf51554d4ba8432333c35a5e3b52705955ede