CVE-2025-7647VulnerabilityPublished 27 Sep 2025Updated 29 Sep 2025

CVE-2025-7647: run-llama/llama_index · Creation of Temporary File With Insecure Permissions

Affects run-llama/llama_indexSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
run-llama run-llama/llama_index	Affected <=0.12.44	Fixed in–

AI-suggested

To mitigate CVE-2025-7647, organizations should first upgrade to a patched version of the llama-index-core package once available. Until then, administrators should implement strict access controls on the /tmp/llama_index directory by setting restrictive permissions (e.g., chmod 700) and ensuring it is owned by the application user to prevent unauthorized access. Employing unique, unpredictable temporary directory names per user or process can reduce the risk of symlink attacks. Running the application in isolated environments such as containers or dedicated virtual machines can limit multi-user exposure. Additionally, monitoring file system changes and access to /tmp/llama_index can help detect suspicious activity. Incorporating mandatory access control (MAC) systems like SELinux or AppArmor to restrict file operations on temporary directories can further harden the environment. Finally, educating developers to avoid hardcoded temporary paths and to use secure temporary file APIs (e.g., mkdtemp) will prevent recurrence.

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.

Impact

For European organizations, especially those deploying run-llama/llama_index on shared Linux servers or multi-tenant environments, this vulnerability poses significant risks. Confidentiality is at high risk as attackers could exfiltrate proprietary AI models or sensitive cached data, potentially exposing intellectual property or sensitive analytics. Integrity is also highly impacted since attackers can poison cached embeddings, leading to corrupted or manipulated AI outputs, which can affect decision-making processes or automated workflows. Availability impact is low but possible if attackers disrupt cache operations. Organizations in sectors relying heavily on AI/ML models—such as finance, healthcare, manufacturing, and research institutions—may face operational and reputational damage if their models are compromised. The vulnerability is particularly concerning in environments where multiple users share the same Linux system, such as cloud-hosted platforms, research clusters, or development servers common in European tech ecosystems.

CWE-378Creation of Temporary File With Insecure Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: High
Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.
Requirements
Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
Implementation
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.
Implementation
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.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Oct 2025, 00:50 UTC

WeaknessesCWE-378

Technical details

References

Community reviews

Related threats