Path Traversal in llama-index-readers-obsidian (CVE-2025-3046)
Summary
Path traversal in llama-index-readers-obsidian (CVE-2025-3046). Confidential information can be exposed externally. Exploitable via ObsidianReader. Mitigation: upgrade to 0.5.1 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-3046 has been found in llama-index-readers-obsidian.
Attackers can target a specific entry point like ObsidianReader over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade llama-index-readers-obsidian to 0.5.1 or later.
If unsure, ask your IT team or search "llama-index-readers-obsidian CVE-2025-3046" on the vendor's site.
CVE-2025-3046 (llama-index-readers-obsidian) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ObsidianReader
Patched: 0.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in llama-index-readers-obsidian. Attackers reach the vulnerable code path via ObsidianReader without authentication.
Check the vendor advisory for the affected versions of llama-index-readers-obsidian. Attack surface: ObsidianReader.
Severity: ?. Confidential information can be exposed externally.
Update to 0.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'llama-index-readers-obsidian' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llama-index-readers-obsidian' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
llama-index-readers-obsidianを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade llama-index-readers-obsidian to 0.5.1ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web huntr.com