Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-3108: A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer co

42
This month
HIGH 7.5UPGRADE

CVE-2025-3108 is a high-severity flaw (CVSS 7.5) affecting llamaindex. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback to Python's pickle module. JsonPickleSerializer prioritizes deserialization using pickle.loads(), which can execute arbitrary code when processing untrusted data. Attackers can exploit this by crafting malicio

Why this priority

  • High severity
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionRequired
EPSS exploit chance0.5% (top 57%)
CISA exploited listNo
WeaknessCWE-1112
Published2025-07-06
Last modified2026-06-17
Publisher (CNA): huntr.dev · Vendor: llamaindex

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

llamaindex llamaindex UPGRADE
Affected: >= 0.12.27 and < 0.12.41
Fixed in: 0.12.41
Safe to downgrade to: a release before 0.12.27
1. Check installed version
apt-cache policy llamaindex || rpm -q llamaindex || llamaindex --version
2. UPGRADE to 0.12.41 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade llamaindex
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade llamaindex
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.12.27 (Debian / Ubuntu)
apt-cache madison llamaindex sudo apt install llamaindex=<VERSION_BEFORE_0.12.27> sudo apt-mark hold llamaindex
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list llamaindex sudo dnf downgrade llamaindex-<VERSION_BEFORE_0.12.27> sudo dnf versionlock add llamaindex
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-3108?

llamaindex: upgrade to 0.12.41. Exact commands for each OS are on this page.

Is CVE-2025-3108 being exploited?

CVE-2025-3108 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-3108 affect?

CVE-2025-3108 affects llamaindex. Severity is high (CVSS 7.5). A critical deserialization vulnerability exists in the run-llama/llama_index library's JsonPickleSerializer component, affecting versions v0.12.27 through v0.12.40. This vulnerability allows remote code execution due to an insecure fallback

How urgent is CVE-2025-3108?

Priority 42/100. High severity; Public exploit reference

Software pages

Python vulnerabilities · OpenAI and LLM tools vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.