How many CVEs have patched __init__?

7 published CVEs changed __init__ in run-llama/llama_index, in 7 distinct patches totalling 105 changed lines, between 2024 and 2026.

What is the latest CVE that changed __init__?

CVE-2025-6208 (Uncontrolled Memory Consumption in run-llama/llama_index), published 2026-02-02, changed lines 251 to 263 of llama-index-core/llama_index/core/readers/file/base.py.

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

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

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

Log in Create an account

run-llama/llama_index

Function

6 files

init

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

Defined in 6 files

Last patched February 2, 2026

7

CVEs

That changed this function

7

Distinct patches

Backports counted once

105

Lines changed

Added plus removed

2024–2026

Years

By CVE publication date

Overview

__init__ in run-llama/llama_index was changed by 7 published CVE fixes between 2024 and 2026, in 7 distinct patches that added or removed 105 lines in total.

The name occurs in 6 files: llama-index-integrations/vector_stores/llama-index-vector-stores-duckdb/llama_index/vector_stores/duckdb/base.py, llama-index-integrations/retrievers/llama-index-retrievers-duckdb-retriever/llama_index/retrievers/duckdb_retriever/base.py, llama-index-core/llama_index/core/exec_utils.py, llama-index-integrations/readers/llama-index-readers-web/llama_index/readers/web/knowledge_base/base.py, llama-index-core/llama_index/core/schema.py, llama-index-core/llama_index/core/readers/file/base.py.

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

CVEs that patched it

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

Uncontrolled Memory Consumption in run-llama/llama_index
CVE-2025-6208 · llama-index-core/llama_index/core/readers/file/base.py · lines 251–263 · +7 −7
Medium · CVSS 5.3
EPSS 0.4%2026-02-02
Arbitrary File Read through Path Traversal in run-llama/llama_index
CVE-2025-6209 · llama-index-core/llama_index/core/schema.py · lines 1260–1267 · +4 −0
High · CVSS 7.5
EPSS 0.6%2025-07-07
SQL Injection in run-llama/llama_index
CVE-2025-1750 · llama-index-integrations/vector_stores/llama-index-vector-stores-duckdb/llama_index/vector_stores/duckdb/base.py · lines 98–147 · +11 −14 in 3 hunks
Critical · CVSS 9.8
EPSS 0.8%2025-06-02
SQL Injection in run-llama/llama_index
CVE-2024-11958 · llama-index-integrations/retrievers/llama-index-retrievers-duckdb-retriever/llama_index/retrievers/duckdb_retriever/base.py · lines 44–56 · +6 −6 in 2 hunks
Critical · CVSS 9.8
EPSS 1.4%2025-03-20
Denial of Service in run-llama/llama_index
CVE-2024-12910 · llama-index-integrations/readers/llama-index-readers-web/llama_index/readers/web/knowledge_base/base.py · lines 40–49 · +2 −0 in 2 hunks
Medium · CVSS 5.9
EPSS 0.7%2025-03-20
llama-index-core Command Injection vulnerability
CVE-2024-3271 · llama-index-core/llama_index/core/exec_utils.py · lines 92–130 · +23 −1
Critical · CVSS 9.8
EPSS 2.9%2024-04-16
llama-index-core Prompt Injection vulnerability leading to Arbitrary Code Execution
CVE-2024-3098 · llama-index-core/llama_index/core/exec_utils.py · lines 92–130 · +23 −1
Critical · CVSS 9.8
EPSS 1.0%2024-04-10

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 files that CVE fixes also changed.

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 _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 load_data2 CVEs · llama-index-core/llama_index/core/readers/json.py

All patched functions in run-llama/llama_index

Frequently asked questions

Common questions about CVE fixes to __init__.

How many CVEs have patched __init__?: 7 published CVEs changed __init__ in run-llama/llama_index, in 7 distinct patches totalling 105 changed lines, between 2024 and 2026.
What is the latest CVE that changed __init__?: CVE-2025-6208 (Uncontrolled Memory Consumption in run-llama/llama_index), published 2026-02-02, changed lines 251 to 263 of llama-index-core/llama_index/core/readers/file/base.py.
How does __init__ compare to the rest of run-llama/llama_index?: run-llama/llama_index has 26 CVEs with a located fix in total; 7 of them changed __init__.
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

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