run-llama llama_index up to 0.12.27 Symbolic Link ObsidianReader path traversal

Summaryinfo

A vulnerability identified as critical has been detected in run-llama llama_index up to 0.12.27. Affected is the function ObsidianReader of the component Symbolic Link Handler. The manipulation leads to path traversal. This vulnerability is traded as CVE-2025-3046. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in run-llama llama_index up to 0.12.27 and classified as critical. This issue affects the function ObsidianReader of the component Symbolic Link Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:

A vulnerability in the `ObsidianReader` class of the run-llama/llama_index repository, versions 0.12.23 to 0.12.28, allows for arbitrary file read through symbolic links. The `ObsidianReader` fails to resolve symlinks to their real paths and does not validate whether the resolved paths lie within the intended directory. This flaw enables attackers to place symlinks pointing to files outside the vault directory, which are then processed as valid Markdown files, potentially exposing sensitive information.

The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2025-3046 since 03/31/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 0.12.28 eliminates this vulnerability. Applying the patch 0008041e8dde8e519621388e5d6f558bde6ef42e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-20216). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• run-llama

Name

• llama_index

Version

• 0.12.0
• 0.12.1
• 0.12.2
• 0.12.3
• 0.12.4
• 0.12.5
• 0.12.6
• 0.12.7
• 0.12.8
• 0.12.9
• 0.12.10
• 0.12.11
• 0.12.12
• 0.12.13
• 0.12.14
• 0.12.15
• 0.12.16
• 0.12.17
• 0.12.18
• 0.12.19
• 0.12.20
• 0.12.21
• 0.12.22
• 0.12.23
• 0.12.24
• 0.12.25
• 0.12.26
• 0.12.27

License

• open-source

Website

• Product: https://github.com/run-llama/llama_index/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion