Path Traversal in llama-index-readers-obsidian (CVE-2025-6210)
Summary
Path traversal in llama-index-readers-obsidian (CVE-2025-6210). Confidential information can be exposed externally. Mitigation: upgrade to 0.5.2 or later.
Original description
The description as published by the source.
A vulnerability in the ObsidianReader class of the run-llama/llama_index repository, specifically in version 0.12.27, allows for hardlink-based path traversal. This flaw permits attackers to bypass path restrictions and access sensitive system files, such as /etc/passwd, by exploiting hardlinks. The vulnerability arises from inadequate handling of hardlinks in the load_data() method, where the security checks fail to differentiate between real files and hardlinks. This issue is resolved in version 0.5.2.
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-6210 has been found in llama-index-readers-obsidian.
Confidential information can be exposed externally.
What to do: upgrade llama-index-readers-obsidian to 0.5.2 or later.
If unsure, ask your IT team or search "llama-index-readers-obsidian CVE-2025-6210" on the vendor's site.
CVE-2025-6210 (llama-index-readers-obsidian) — CWE-22
Attack vector: local / unauthenticated / no user interaction
Patched: 0.5.2 — 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.
Check the vendor advisory for the affected versions of llama-index-readers-obsidian.
Severity: ?. Confidential information can be exposed externally.
Update to 0.5.2.
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.2ステージング環境で 0.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 huntr.com