OS Command Injection in llama-index-cli (CVE-2025-1753)
Summary
OS command injection in llama-index-cli (CVE-2025-1753). Successful exploitation can lead to full system takeover. Exploitable via os.system. Mitigation: upgrade to 0.4.1 or later.
Original description
The description as published by the source.
LLama-Index CLI version v0.12.20 contains an OS command injection vulnerability. The vulnerability arises from the improper handling of the --files argument, which is directly passed into os.system. An attacker who controls the content of this argument can inject and execute arbitrary shell commands. This vulnerability can be exploited locally if the attacker has control over the CLI arguments, and remotely if a web application calls the LLama-Index CLI with a user-controlled filename. This issue can lead to arbitrary code execution on the affected system.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-1753 has been found in llama-index-cli.
Attackers can target a specific entry point like os.system over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade llama-index-cli to 0.4.1 or later.
If unsure, ask your IT team or search "llama-index-cli CVE-2025-1753" on the vendor's site.
CVE-2025-1753 (llama-index-cli) — CWE-78
Attack vector: local / no user interaction
Attack surface: os.system
Patched: 0.4.1 — apply immediately
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.
OS command injection (CWE-78) exists in llama-index-cli. Attackers reach the vulnerable code path via os.system.
Check the vendor advisory for the affected versions of llama-index-cli. Attack surface: os.system.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 0.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'llama-index-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llama-index-cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
llama-index-cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade llama-index-cli to 0.4.1ステージング環境で 0.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web huntr.com