CVE-2025-3046: LlamaIndex Obsidian: symlink traversal exposes host files
GHSA-fmrf-6jv9-qjc7 HIGH CISA: TRACK*LlamaIndex's ObsidianReader blindly follows symlinks without path validation, letting anyone who can write to a vault directory read arbitrary host files during document ingestion. Patch to llama-index-readers-obsidian 0.5.1 immediately. This is especially dangerous in RAG pipelines where vault content is untrusted, shared, or synced from external sources.
Risk Assessment
CVSS 7.5 with no authentication, no user interaction, and low attack complexity makes exploitation straightforward for any attacker with write access to the vault directory. EPSS 0.00142 indicates no current active exploitation. Risk is elevated in multi-tenant setups, CI/CD pipelines auto-ingesting Obsidian vaults, or any deployment where vault content originates from untrusted parties. Absence from CISA KEV lowers urgency slightly, but the zero-friction exploitation path warrants prompt patching.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| llama-index-readers-obsidian | pip | < 0.5.1 | 0.5.1 |
Do you use llama-index-readers-obsidian? You're affected.
Severity & Risk
Attack Surface
Recommended Action
5 steps-
Upgrade llama-index-readers-obsidian to >= 0.5.1 immediately.
-
Audit vault directories for unexpected symlinks:
find <vault_dir> -type l. -
Run ingestion processes in containers or chrooted environments with filesystem access limited to the vault path.
-
If immediate upgrade is blocked, pre-scan vault contents by resolving all symlink targets and rejecting paths outside the vault root before invoking ObsidianReader.
-
Review existing vector store contents for anomalous data (credentials, config fragments) that may have been ingested prior to patching.
CISA SSVC Assessment
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2025-3046?
LlamaIndex's ObsidianReader blindly follows symlinks without path validation, letting anyone who can write to a vault directory read arbitrary host files during document ingestion. Patch to llama-index-readers-obsidian 0.5.1 immediately. This is especially dangerous in RAG pipelines where vault content is untrusted, shared, or synced from external sources.
Is CVE-2025-3046 actively exploited?
No confirmed active exploitation of CVE-2025-3046 has been reported, but organizations should still patch proactively.
How to fix CVE-2025-3046?
1. Upgrade llama-index-readers-obsidian to >= 0.5.1 immediately. 2. Audit vault directories for unexpected symlinks: `find <vault_dir> -type l`. 3. Run ingestion processes in containers or chrooted environments with filesystem access limited to the vault path. 4. If immediate upgrade is blocked, pre-scan vault contents by resolving all symlink targets and rejecting paths outside the vault root before invoking ObsidianReader. 5. Review existing vector store contents for anomalous data (credentials, config fragments) that may have been ingested prior to patching.
What systems are affected by CVE-2025-3046?
This vulnerability affects the following AI/ML architecture patterns: RAG pipelines, document ingestion pipelines, knowledge base loaders, agent frameworks.
What is the CVSS score for CVE-2025-3046?
CVE-2025-3046 has a CVSS v3.1 base score of 7.5 (HIGH). The EPSS exploitation probability is 0.49%.
Technical Details
NVD Description
A vulnerability in the `ObsidianReader` class in LlamaIndex Readers Integration: Obsidian before version 0.5.1 from 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.
Exploitation Scenario
An attacker with write access to an Obsidian vault — via a compromised sync service (e.g., iCloud Drive, Git repo), shared network folder, or insider — places a symlink: `vault/notes.md -> /home/appuser/.env`. When the LlamaIndex ingestion job runs, ObsidianReader processes the symlink as a valid Markdown file and loads the .env contents into the RAG vector store. A downstream query such as 'list API keys in use' surfaces the credentials via normal LLM response. The attacker never touches the application directly — vault write access is the only requirement.
Weaknesses (CWE)
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N References
- github.com/advisories/GHSA-fmrf-6jv9-qjc7
- github.com/run-llama/llama_index/commit/0008041e8dde8e519621388e5d6f558bde6ef42e
- github.com/run-llama/llama_index/commit/266eb3b3a61f158112726d75a5f5f0b90e34ded0
- github.com/run-llama/llama_index/pull/18320
- huntr.com/bounties/90a1f1b2-bb82-4d66-9fc1-856ed5f904da
- nvd.nist.gov/vuln/detail/CVE-2025-3046
Timeline
Related Vulnerabilities
CVE-2024-12909 10.0 llama-index finchat: SQL injection enables RCE
Same package: llama-index CVE-2024-11958 9.8 llama-index DuckDB retriever: SQLi enables RCE
Same package: llama-index CVE-2025-1793 9.8 llama_index: SQL injection in vector store integrations
Same package: llama-index CVE-2025-1753 7.8 llama-index-cli: OS command injection enables RCE
Same package: llama-index CVE-2025-3225 7.5 llama-index Papers Loader: XML expansion DoS
Same package: llama-index
AI Threat Alert