How many CVEs have patched ObsidianReader?

1 published CVEs changed ObsidianReader in run-llama/llama_index, in 1 distinct patches totalling 2 changed lines, between 2025 and 2025.

What is the latest CVE that changed ObsidianReader?

CVE-2025-3046 (Path Traversal via Symbolic Links in run-llama/llama_index), published 2025-07-07, changed lines 29 to 30 of llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py.

How does ObsidianReader compare to the rest of run-llama/llama_index?

run-llama/llama_index has 26 CVEs with a located fix in total; 1 of them changed ObsidianReader.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Run Llama
Llama_index
ObsidianReader

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Run Llama
Llama_index
ObsidianReader

ObsidianReader in run-llama/llama_index: Patched by 1 CVEs

run-llama/llama_index

Class

ObsidianReader

Name: ObsidianReader in run-llama/llama_index: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py

Last patched July 7, 2025

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

ObsidianReader in run-llama/llama_index was changed by 1 published CVE fixes in 2025, in 1 distinct patches that added or removed 2 lines in total.

run-llama/llama_index has 26 CVEs with a located fix in total, so 4% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed ObsidianReader, newest first, with the lines each fix touched.

Path Traversal via Symbolic Links in run-llama/llama_index
CVE-2025-3046 · lines 29–30 · +1 −1
High · CVSS 7.5
EPSS 0.6%2025-07-07

Get an alert when the next CVE fix lands in run-llama/llama_index, with the patched functions.

Monitor llama_index CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1load_datallama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py2 CVEs · 2 patches2025
2is_hardlinkllama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py1 CVEs · 1 patches2025

Other hotspots in the repository

Functions in run-llama/llama_index changed by the most CVE fixes.

default_formatter3 CVEs · llama-index-core/llama_index/core/agent/workflow/react_agent.py load_data2 CVEs · llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py get_article_urls2 CVEs · llama-index-integrations/readers/llama-index-readers-web/llama_index/readers/web/knowledge_base/base.py __init__2 CVEs · llama-index-core/llama_index/core/exec_utils.py _verify_source_safety2 CVEs · llama-index-core/llama_index/core/exec_utils.py _restricted_import2 CVEs · llama-index-core/llama_index/core/exec_utils.py

All patched functions in run-llama/llama_index

Frequently asked questions

Common questions about CVE fixes to ObsidianReader.

How many CVEs have patched ObsidianReader?: 1 published CVEs changed ObsidianReader in run-llama/llama_index, in 1 distinct patches totalling 2 changed lines, between 2025 and 2025.
What is the latest CVE that changed ObsidianReader?: CVE-2025-3046 (Path Traversal via Symbolic Links in run-llama/llama_index), published 2025-07-07, changed lines 29 to 30 of llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py.
How does ObsidianReader compare to the rest of run-llama/llama_index?: run-llama/llama_index has 26 CVEs with a located fix in total; 1 of them changed ObsidianReader.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

llama-index-integrations/readers/llama-index-readers-obsidian/llama_index/readers/obsidian/base.py on GitHub (opens in a new tab)
All patched functions in run-llama/llama_index
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track run-llama/llama_index CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References