CVE-2025-1753

CVE-2025-1753 is a high-severity OS command injection vulnerability in llama-index-cli (pip), affecting versions < 0.4.1. It is fixed in 0.4.1.

Summary

LLama-Index CLI prior to v0.4.1, corresponding to LLama-Index prior to v0.12.21, 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.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2025-1753 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.1); upgrading removes the vulnerable code path.

Affected versions

llama-index-cli (< 0.4.1)

Security releases

llama-index-cli → 0.4.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade llama-index-cli to 0.4.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-1753? CVE-2025-1753 is a high-severity OS command injection vulnerability in llama-index-cli (pip), affecting versions < 0.4.1. It is fixed in 0.4.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
  2. How severe is CVE-2025-1753? CVE-2025-1753 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of llama-index-cli are affected by CVE-2025-1753? llama-index-cli (pip) versions < 0.4.1 is affected.
  4. Is there a fix for CVE-2025-1753? Yes. CVE-2025-1753 is fixed in 0.4.1. Upgrade to this version or later.
  5. Is CVE-2025-1753 exploitable, and should I be worried? Whether CVE-2025-1753 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2025-1753 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2025-1753? Upgrade llama-index-cli to 0.4.1 or later.

Other vulnerabilities in llama-index-cli

Stop the waste.
Protect your environment with Kodem.