Skip to content

← Public intelligence

PyPI package

llama-index-readers-obsidian

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.2PyPIAmendedPublished

    LlamaIndex vulnerability in its ObsidianReader class can lead to Path Traversal exploit

    CVE-2025-6210 · GHSA-3j8r-jf9w-5cmh

    Affected
    • PyPI llama-index-readers-obsidian < 0.5.2
    Fixed in
    0.5.2· Vendor fix available
    Issue
    A vulnerability in the ObsidianReader class of the run-llama/llamaindex repository, before version 0.5.2 (specifically in version 0.12.27 of llama-index), 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 loaddata() method, where the security checks fail to differentiate between real files and hardlinks. This issue is resolved in llama-index-readers-obsidian version 0.5.2.

    Recommended action: Upgrade to 0.5.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)osv.dev (2)github.com (3)Source checked Evidence →
  2. High, CVSS 7.5PyPIAmendedPublished

    LlamaIndex is vulnerable to Path Traversal attack through its ObsidianReader class

    CVE-2025-3046 · GHSA-fmrf-6jv9-qjc7

    Affected
    • PyPI llama-index-readers-obsidian < 0.5.1
    Fixed in
    0.5.1· Vendor fix available
    Issue
    A vulnerability in the ObsidianReader class in LlamaIndex Readers Integration: Obsidian before version 0.5.1 from the run-llama/llamaindex 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.

    Recommended action: Upgrade to 0.5.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)osv.dev (2)github.com (3)Source checked Evidence →