llama-index has Insecure Temporary File
CVE-2025-7707 · GHSA-rg9h-vx28-xxp5 · published 2025-10-13
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.19%
- Fixed in
- 0.13.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
The llama_index library version 0.12.33 sets the NLTK data directory to a subdirectory of the codebase by default, which is world-writable in multi-user environments. This configuration allows local users to overwrite, delete, or corrupt NLTK data files, leading to potential denial of service, data tampering, or privilege escalation. The vulnerability arises from the use of a shared cache directory instead of a user-specific one, making it susceptible to local data tampering and denial of service.
Upgrade llama-index to 0.13.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| llama-index | PyPI | < 0.13.0 | 0.13.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- Criticalllama_index vulnerable to SQL Injectionllama-index
- CriticalSQL injection in llama-indexllama-index
- Criticalllama-index vulnerable to arbitrary code executionllama-index
- HighLlamaIndex Vulnerable to Denial of Service (DoS)llama-index
- HighLlamaIndex vulnerable to Creation of Temporary File in Directory with Insecure Permissionsllama-index
- HighRunGptLLM class in LlamaIndex has a command injectionllama-index
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.