run-llama/llama_index: Creation of Temporary File With Insecure Permissions
CVE-2025-7647 is a high-severity creation of temporary file with insecure permissions vulnerability in run-llama/llama_index from Run-llama, with a CVSS 3.0 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version v0.13.0 as the first without the flaw, so updating run-llama/llama_index to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update run-llama/llama_index to v0.13.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Run-llama | run-llama/llama_index | before v0.13.0 | v0.13.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (huntr.dev).
Official description
The llama-index-core package, up to version 0.12.44, contains a vulnerability in the `get_cache_dir()` function where a predictable, hardcoded directory path `/tmp/llama_index` is used on Linux systems without proper security controls. This vulnerability allows attackers on multi-user systems to steal proprietary models, poison cached embeddings, or conduct symlink attacks. The issue affects all Linux deployments where multiple users share the same system. The vulnerability is classified under CWE-379, CWE-377, and CWE-367, indicating insecure temporary file creation and potential race conditions.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Creation of Temporary File With Insecure Permissions
Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.
How developers prevent this class of flaw
- Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
- Ensure that you use proper file permissions. This can be achieved by using a safe temp file function. Temporary files should be writable and readable only by the process that owns the file.
- Randomize temporary file names. This can also be achieved by using a safe temp-file function. This will ensure that temporary files will not be created in predictable places.
More Creation of Temporary File With Insecure Permissions vulnerabilities (CWE-378)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Other vulnerabilities in run-llama/llama_index
- 7.8 High severity
- 8.6 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Creation of Temporary File With Insecure Permissions vulnerabilities
- 7.4 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.9 Critical severity
Spotted an error? Tell us.