Skip to content
Fencer Vulns
high 7.8

CVE-2025-1753 json

Command Injection in LLama-Index CLI in run-llama/llama_index

published 2025-05-28 17 mo ago modified 2026-07-13 3 mo ago also GHSA-g99h-56mw-8263 , PYSEC-2025-246 , PYSEC-2026-1557 , EUVD-2025-16322

cvss
7.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi llama-index-cli 0.4.1
  • run-llama run-llama/llama_index 0.4.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-1753 updated cvss 7.8

llama-index: Command Injection in LLama-Index CLI in run-llama/llama_index

  • Red Hat OpenShift Lightspeed openshift-lightspeed-tech-preview/lightspeed-service-api-rhel9
    affected: no fix available
  • Red Hat Ansible Automation Platform 2 aap-cloud-metrics-collector-container, ansible-automation-platform-24/de-minimal-rhel8, ansible-automation-platform-24/de-minimal-rhel9, ansible-automation-platform-24/lightspeed-rhel8, ansible-automation-platform-25/de-minimal-rhel8, ansible-automation-platform-25/de-minimal-rhel9, +5 more
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
17 mo ago

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.com https://huntr.com/bounties/19e1c67e-1d77-451d-b10b-acbe99900b22 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi llama-index-cli
<0.4.1
0.4.1
pypi llama-index
<=0.12.20
 no fix listed

Affected products

  • run-llama run-llama/llama_index

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.