Categories
CVE-2025-3044

Vulnerability in llama-index-readers-papers (CVE-2025-3044)

Summary

Vulnerability in llama-index-readers-papers (CVE-2025-3044). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.3.1 or later.

Original description

The description as published by the source.

A vulnerability in the ArxivReader class of the run-llama/llama_index repository allows for MD5 hash collisions when generating filenames for downloaded papers. This can lead to data loss as papers with identical titles but different contents may overwrite each other, preventing some papers from being processed for AI model training. The issue is resolved in llama-index-readers-papers version 0.3.1 (in llama-index 0.12.28).

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-3044 has been found in llama-index-readers-papers.
Risk of unauthorized operations or information disclosure.
What to do: upgrade llama-index-readers-papers to 0.3.1 or later.
If unsure, ask your IT team or search "llama-index-readers-papers CVE-2025-3044" on the vendor's site.

CVE-2025-3044 (llama-index-readers-papers) — CWE-440
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.3.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.

❓ What is the problem

A vulnerability (CWE-440) exists in llama-index-readers-papers.

📍 Affected scope

Check the vendor advisory for the affected versions of llama-index-readers-papers.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.3.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'llama-index-readers-papers' . 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

  1. 1
    Identify exposure identify
    grep -r 'llama-index-readers-papers' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で llama-index-readers-papers を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade llama-index-readers-papers to 0.3.1

    ステージング環境で 0.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI llama-index-readers-papers
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details